Age | Commit message (Collapse) | Author | Files | Lines |
|
Right now there is no convenient way to check if a process is being
coredumped at the moment.
It might be necessary to recognize such state to prevent killing the
process and getting a broken coredump. Writing a large core might take
significant time, and the process is unresponsive during it, so it might
be killed by timeout, if another process is monitoring and
killing/restarting hanging tasks.
We're getting a significant number of corrupted coredump files on
machines in our fleet, just because processes are being killed by
timeout in the middle of the core writing process.
We do have a process health check, and some agent is responsible for
restarting processes which are not responding for health check requests.
Writing a large coredump to the disk can easily exceed the reasonable
timeout (especially on an overloaded machine).
This flag will allow the agent to distinguish processes which are being
coredumped, extend the timeout for them, and let them produce a full
coredump file.
To provide an ability to detect if a process is in the state of being
coredumped, we can expose a boolean CoreDumping flag in
/proc/pid/status.
Example:
$ cat core.sh
#!/bin/sh
echo "|/usr/bin/sleep 10" > /proc/sys/kernel/core_pattern
sleep 1000 &
PID=$!
cat /proc/$PID/status | grep CoreDumping
kill -ABRT $PID
sleep 1
cat /proc/$PID/status | grep CoreDumping
$ ./core.sh
CoreDumping: 0
CoreDumping: 1
[guro@fb.com: document CoreDumping flag in /proc/<pid>/status]
Link: http://lkml.kernel.org/r/20170928135357.GA8470@castle.DHCP.thefacebook.com
Link: http://lkml.kernel.org/r/20170920230634.31572-1-guro@fb.com
Signed-off-by: Roman Gushchin <guro@fb.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Konstantin Khlebnikov <koct9i@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[k.lewandowsk: backport mainline commit c643401218 for userspace process managers
(eg. resourced) to be able to avoid killing dead processes, breaking crash reports]
Signed-off-by: Karol Lewandowski <k.lewandowsk@samsung.com>
Change-Id: I5ba2fcbf4f388be752db542e80ebca367dba618c
|
|
Change-Id: Id0c825b35e6535a83cad928f85378d234305dfe1
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
|
|
Until Tizen 5.0, for detent/bezel input device, its event value
was in between -2 and 2, but value 1, meant starting movement to
counter clockwise or clockwise, and value -1, meant moving back
to original position, never used. Change event value of the
detent/bezel device for Tizen 5.5 and later version.
It changes detent/bezel input driver event interface, so user
input framework for detent/bezel input should be also changed.
Ref: https://review.tizen.org/gerrit/#/c/platform/upstream/enlightenment/+/220346/
Change-Id: Iaa8e76de94eb4254820d93865dab9d4f7006f4e4
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
|
|
This reverts commit d6d59e55d57a20532fcadd25d8eb061086a6c6b9.
Change-Id: Id758905c7a4cb0e8dd7a752f9a2e378c79d93fd3
|
|
Change-Id: I94076d97c02adb40b811ec985ad87abd0cbd74be
Signed-off-by: Dongkyun Son <dongkyun.s@samsung.com>
|
|
Change-Id: I83dba3f6ab98fd27e48c10f2783d5b7297323195
Signed-off-by: Andrey Kazmin <a.kazmin@partner.samsung.com>
|
|
Change-Id: I87565fde5a245f813dde58164220e52647647a89
Signed-off-by: Andrey Kazmin <a.kazmin@partner.samsung.com>
|
|
commit 38c7b224ce22c25fed04007839edf974bd13439d upstream.
New versions of gcc reasonably warn about the odd pattern of
strncpy(p, q, strlen(q));
which really doesn't make sense: the strncpy() ends up being just a slow
and odd way to write memcpy() in this case.
There was a comment about _why_ the code used strncpy - to avoid the
terminating NUL byte, but memcpy does the same and avoids the warning.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[dongkyun.s: cherry-pick stable linux-4.9.y commit 37370fadd2da for gcc 9 build]
Change-Id: I2f005aa7c6642d76d818f1fda7722f345095b8a9
|
|
When building with gcc-7, the following warning happens:
drivers/gpu/drm/i915/intel_uncore.c: In function ‘hsw_unclaimed_reg_detect’:
drivers/gpu/drm/i915/intel_uncore.c:638:36: warning: decrement of a boolean expression [-Wbool-operation]
i915.mmio_debug = mmio_debug_once--;
^~
As it's really not wise to -- on a boolean value.
Commit 7571494004d8 ("drm/i915: Do one shot unclaimed mmio detection
less frequently") which showed up in 4.6-rc1 does solve this issue, by
rewriting the mmio detection logic, but that isn't really good to
backport to 4.4-stable, so just fix up the obvious logic here to do the
right thing.
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Paulo Zanoni <przanoni@gmail.com>
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[dongkyun.s: cherry-pick stable linux-4.4.y commit c81c4d453edf for gcc 9 build]
Change-Id: I6094687ed5887de09f25175c1be63422651fcd03
|
|
Starting with GCC 9, -Warray-bounds detects cases when memset is called
starting on a member of a struct but the size to be cleared ends up
writing over further members.
Such a call happens in the trace code to clear, at once, all members
after and including `seq` on struct trace_iterator:
In function 'memset',
inlined from 'ftrace_dump' at kernel/trace/trace.c:8914:3:
./include/linux/string.h:344:9: warning: '__builtin_memset' offset
[8505, 8560] from the object at 'iter' is out of the bounds of
referenced subobject 'seq' with type 'struct trace_seq' at offset
4368 [-Warray-bounds]
344 | return __builtin_memset(p, c, size);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In order to avoid GCC complaining about it, we compute the address
ourselves by adding the offsetof distance instead of referring
directly to the member.
Since there are two places doing this clear (trace.c and trace_kdb.c),
take the chance to move the workaround into a single place in
the internal header.
Link: http://lkml.kernel.org/r/20190523124535.GA12931@gmail.com
Signed-off-by: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
[ Removed unnecessary parenthesis around "iter" ]
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
[dongkyun.s: cherry-pick mainline commit 0c97bf863efc for gcc 9 build]
Change-Id: I81e1711b2009e9b8da6f9808362e1c4376066e1f
|
|
We already did this for clang, but now gcc has that warning too. Yes,
yes, the address may be unaligned. And that's kind of the point.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[a.kazmin: cherry-pick mainline commit 6f303d60534c4 for gcc 9 build]
Signed-off-by: Andrey Kazmin <a.kazmin@partner.samsung.com>
Change-Id: I43cefa7a44a5cdb299ef4a8c97d2f45d7dd999e2
|
|
On one hand commit 28644c809f44 ("regmap: Add the rbtree cache support")
added 'regcache_rbtree_node' as packed structure, while on the other hand
commit e977145aeaad ("[RBTREE] Add explicit alignment to sizeof(long)
for struct rb_node.") declared struct 'rb_node' as aligned.
Solve the ambiguity of placing aligned structure in a packed one by
removing the packed attribute from struct. This seems to be the behavior
of gcc anyway.
This removes the following warning (W=1):
drivers/base/regmap/regcache-rbtree.c:36:1: warning: alignment 1 of 'struct regcache_rbtree_node' is less than 4 [-Wpacked-not-aligned]
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: Mathieu Malaterre <malat@debian.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
[dongkyun.s: cherry-pick mainline commit 435bba0f11f0 for gcc 9 build]
Change-Id: I27907a2c60b6fd82a28fc7321c393ce0abb335fd
|
|
In file included from scripts/kconfig/zconf.tab.c:2485:
scripts/kconfig/confdata.c: In function ‘conf_write’:
scripts/kconfig/confdata.c:773:22: warning: ‘%s’ directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
sprintf(newname, "%s%s", dirname, basename);
^~
scripts/kconfig/confdata.c:773:19: note: assuming directive output of 7 bytes
sprintf(newname, "%s%s", dirname, basename);
^~~~~~
scripts/kconfig/confdata.c:773:2: note: ‘sprintf’ output 1 or more bytes (assuming 4104) into a destination of size 4097
sprintf(newname, "%s%s", dirname, basename);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
scripts/kconfig/confdata.c:776:23: warning: ‘.tmpconfig.’ directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
^~~~~~~~~~~
scripts/kconfig/confdata.c:776:3: note: ‘sprintf’ output between 13 and 4119 bytes into a destination of size 4097
sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Increase the size of tmpname and newname to make GCC happy.
Cc: stable@vger.kernel.org
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
[dongkyun.s: cherry-pick mainline commit 2ae89c7a82ea for gcc 9 build]
Change-Id: Ia23bce123ec869c6030867cdf65e0cac64d43441
|
|
I made the mistake of upgrading my desktop to the new Fedora 26 that
comes with gcc-7.1.1.
There's nothing wrong per se that I've noticed, but I now have 1500
lines of warnings, mostly from the new format-truncation warning
triggering all over the tree.
We use 'snprintf()' and friends in a lot of places, and often know that
the numbers are fairly small (ie a controller index or similar), but gcc
doesn't know that, and sees an 'int', and thinks that it could be some
huge number. And then complains when our buffers are not able to fit
the name for the ten millionth controller.
These warnings aren't necessarily bad per se, and we probably want to
look through them subsystem by subsystem, but at least during the merge
window they just mean that I can't even see if somebody is introducing
any *real* problems when I pull.
So warnings disabled for now.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[a.kazmin: cherry-pick mainline commit bd664f6b3e376 for gcc 9 build]
Signed-off-by: Andrey Kazmin <a.kazmin@partner.samsung.com>
Change-Id: I5d839f1b41d5a8b7977e133a28c038549bf772b0
|
|
gcc-7 has an "optimization" pass that completely screws up, and
generates the code expansion for the (impossible) case of calling
ilog2() with a zero constant, even when the code gcc compiles does not
actually have a zero constant.
And we try to generate a compile-time error for anybody doing ilog2() on
a constant where that doesn't make sense (be it zero or negative). So
now gcc7 will fail the build due to our sanity checking, because it
created that constant-zero case that didn't actually exist in the source
code.
There's a whole long discussion on the kernel mailing about how to work
around this gcc bug. The gcc people themselevs have discussed their
"feature" in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72785
but it's all water under the bridge, because while it looked at one
point like it would be solved by the time gcc7 was released, that was
not to be.
So now we have to deal with this compiler braindamage.
And the only simple approach seems to be to just delete the code that
tries to warn about bad uses of ilog2().
So now "ilog2()" will just return 0 not just for the value 1, but for
any non-positive value too.
It's not like I can recall anybody having ever actually tried to use
this function on any invalid value, but maybe the sanity check just
meant that such code never made it out in public.
Reported-by: Laura Abbott <labbott@redhat.com>
Cc: John Stultz <john.stultz@linaro.org>,
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[a.kazmin: cherry-pick mainline commit 474c90156c8d for gcc 9 build]
Signed-off-by: Andrey Kazmin <a.kazmin@partner.samsung.com>
Change-Id: I4cffaa9b5dfd2064413648f22686960269a2406b
|
|
gcc-7 caught what it considers a NULL pointer dereference:
sound/pci/hda/patch_ca0132.c: In function 'dspio_scp.constprop':
sound/pci/hda/patch_ca0132.c:1487:4: error: argument 1 null where non-null expected [-Werror=nonnull]
This is plausible from looking at the function, as we compare 'reply'
to NULL earlier in it. I have not tried to analyze if there are constraints
that make it impossible to hit the bug, but adding another NULL check in
the end kills the warning and makes the function more robust.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
[dongkyun.s: cherry-pick mainline commit 46a049dae771 for gcc 9 build]
Change-Id: Id0faddb2d8b93b5b9aa522ae7ef08c34886df5e6
|
|
gcc-7 warns:
In file included from arch/x86/tools/relocs_64.c:17:0:
arch/x86/tools/relocs.c: In function ‘process_64’:
arch/x86/tools/relocs.c:953:2: warning: argument 1 null where non-null expected [-Wnonnull]
qsort(r->offset, r->count, sizeof(r->offset[0]), cmp_relocs);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from arch/x86/tools/relocs.h:6:0,
from arch/x86/tools/relocs_64.c:1:
/usr/include/stdlib.h:741:13: note: in a call to function ‘qsort’ declared here
extern void qsort
This happens because relocs16 is not used for ELF_BITS == 64,
so there is no point in trying to sort it.
Make the sort_relocs(&relocs16) call 32bit only.
Signed-off-by: Markus Trippelsdorf <markus@trippelsdorf.de>
Link: http://lkml.kernel.org/r/20161215124513.GA289@x4
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
[dongkyun.s: cherry-pick mainline commit 7ebb91678294 for gcc 9 build]
Change-Id: I1d521280f297d09a8a93af70cf3039e86b2b86e5
|
|
security-manager is responsible for the internet privilage using
iptables and the following functionalities are required:
- iptables match owner
- iptables logging
- iptables limiting
- corresponding IPV6 equivalents, incl conntrack
Change-Id: I3ef34a69b8495f4ea0390de601b5623d55df6400
|
|
The XT_OWNER_SUPPL_GROUPS flag causes GIDs specified with XT_OWNER_GID
to be also checked in the supplementary groups of a process.
f_cred->group_info cannot be modified during its lifetime and f_cred
holds a reference to it so it's safe to use.
Signed-off-by: Lukasz Pawelczyk <l.pawelczyk@samsung.com>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
backport from mainline to apply supplementary groups on netfilter
Change-Id: I900d03042c82b4d5f13dec7695e4b1eba7f2aa74
(cherry picked from commit e7a26f2b0e8021c9415f0b92caf9538974720855)
|
|
|
|
Change-Id: Ic83f49e526d564977622f69ff907fb6d928dc161
Signed-off-by: Rahul Dadhich <r.dadhich@samsung.com>
(cherry picked from commit 97424c551a9eb8f44806da4fa6f7441c88c41f01)
|
|
Change-Id: I7d9d4d5a53e509c1aa7adfed6e577b6974b1c4a1
Signed-off-by: Rahul Dadhich <r.dadhich@samsung.com>
(cherry picked from commit 660cfa1e6e9470b5e96bb55f9732a2f2d4c46718)
|
|
OpenSSL 1.0.2 will be deprecated from Tizen, so, this commit is required to
migrate to version 1.1.
Change-Id: I2d698860fe585b817f958e29491b85544aeea063
Signed-off-by: Dongkyun Son <dongkyun.s@samsung.com>
|
|
This reverts commit 05b43540ba2d03ff54a81e5762ef614f4cfe2a7c.
Change-Id: I867b83d86161fd3a91a71002cbfcd9dadd9498f8
Signed-off-by: manish.r <manish.r@samsung.com>
|
|
This reverts commit 4664ea135fc55ef5bcfb5e255fbeabe3e3484e79.
Change-Id: Ia029c6429d4596482bd448c408d915bb3db2e89c
Signed-off-by: manish.r <manish.r@samsung.com>
|
|
tizen
|
|
Change-Id: I92d0ca690f6f34d2b4f5d4d77c0591b9fa6e5de8
Signed-off-by: manish.r <manish.r@samsung.com>
|
|
Change-Id: I4d5bbbda615ad63896eeff232831b865b76bf569
Signed-off-by: kumudhakn <kumudha.n@samsung.com>
|
|
Change-Id: Id48d629eed926ad6d272d55fbcd8f953fd466dd0
Signed-off-by: kumudhakn <kumudha.n@samsung.com>
|
|
Change-Id: Ia41f133eedb75797d37e47d8d4995bcab643abf9
Signed-off-by: Rahul Dadhich <r.dadhich@samsung.com>
|
|
Change-Id: Ibbb0012b71dc6dc302ae3fc35d96b19fd0c2f34f
Signed-off-by: Karthik Bhat <kv.bhat@samsung.com>
|
|
Change-Id: I5acfbfef1a97a7785523b848fd7a5c3678a3261f
Signed-off-by: Karthik Bhat <kv.bhat@samsung.com>
|
|
Change-Id: Ib779e7096f40a8b9660cfa31e2337db2646619cc
Signed-off-by: Rahul Dadhich <r.dadhich@samsung.com>
|
|
Change-Id: I558a2e00c077d6c19de82acb4214d39999034c7f
Signed-off-by: Vladislav Andresov <v.andresov@partner.samsung.com>
(cherry picked from commit f6fd5336d495cf1f731c85d041e79cf3cf3a8e2b)
|
|
Change-Id: I6108df4d6342add2b866a15c78ea3878fb1df189
Signed-off-by: Karthik Bhat <kv.bhat@samsung.com>
|
|
Currently convert ioctl is using for
surfaces with different formats.
Change-Id: I7c4d640bd43efcd305e49aae42231556a9129181
Signed-off-by: Vladislav Andresov <v.andresov@partner.samsung.com>
|
|
|
|
Change-Id: Id2c19096cd568216c54134a1b9c4ac2e16cdfa43
Signed-off-by: Rahul Dadhich <r.dadhich@samsung.com>
|
|
Change-Id: I9c2ee31d4dd1f62e07dab0d9bce20429fa55a743
Signed-off-by: Rahul Dadhich <r.dadhich@samsung.com>
|
|
This PR is to remove unnecessary and duplicated spec files.
And, it is to activate the kernel image (bzImage) and System
map file (System.map) with gbs build as well as build scripts
such as build_x86.sh and build_x86_64.sh.
**Changes proposed in this PR:**
* Changelog v3:
1. Appended symbolic link with /usr/src/linux-headers for compatibility
* Changelog v2:
1. Applied the comments of @Mikhail Labiuk and @MyungJoo Ham
* Changelog v1:
1. bzImage is used to run emulator rootfs based on QEMU/KVM
2. System.map is used to do debugging kernel functions
3. Removed unnecessary spec files
4. Integrated the spec files into one spec file for consistency
5. Added kernel-headers rpm to support kernel module build of arm/aarch64
**Self assessment:**
1. GBS build: Passed
1. OBS build: Passed (manually)
**How to evaluate:**
1. x86/32bit: time gbs build -A i586 --clean --include-all --define "with emulator"
2. x86/64bit: time gbs build -A x86_64 --clean --include-all --define "with emulator"
3. arm/32bit: time gbs build -A armv7l --clean --include-all --define "with emulator"
4. arm/64bit: time gbs build -A aarch64 --clean --include-all --define "with emulator"
**After this PR:**
$ ls -al /home/leemgs/GBS-ROOT-4.0/local/repos/tizen/i586/RPMS
drwxrwxr-x 2 invain invain 4096 4월 10 17:16 .
drwxrwxr-x 6 invain invain 4096 4월 10 17:16 ..
-rw-rw-r-- 2 invain invain 7175827 4월 10 17:15 emulator-kernel-4.4.35-0.i686.rpm
-rw-rw-r-- 2 invain invain 338716 4월 10 17:15 emulator-kernel-debugsource-4.4.35-0.i686.rpm
-rw-rw-r-- 2 invain invain 59980920 4월 10 17:15 emulator-kernel-devel-4.4.35-0.i686.rpm
-rw-rw-r-- 2 invain invain 1936999 4월 10 17:16 emulator-kernel-devel-debuginfo-4.4.35-0.i686.rpm
-rw-rw-r-- 2 invain invain 580448 4월 10 17:15 emulator-kernel-modules-4.4.35-0.i686.rpm
-rw-rw-r-- 2 invain invain 1026336 4월 10 17:15 emulator-kernel-perf-4.4.35-0.i686.rpm
-rw-rw-r-- 2 invain invain 1721079 4월 10 17:16 emulator-kernel-perf-debuginfo-4.4.35-0.i686.rpm
-rw-rw-r-- 2 invain invain 883864 4월 10 17:15 emulator-kernel-user-headers-4.4.35-0.i686.rpm
Change-Id: I80607659c6fb66ee45ccd2d683d23c9f2c642cfc
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
|
|
In SPIN / AD project, we are going to support arm as well.
Change-Id: Id1b509a03300e010224da077080ba5376ec3b548
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
|
|
Change-Id: I9775ef977d8807d5a0ca6acb0fbf4446eebe04d4
Signed-off-by: jihye424.kim <jihye424.kim@samsung.com>
|
|
Kernel objects (kernel module objects) build requires
headers and Makefiles. This is to be noarch as well.
Soon, we need to create JIRA-TRE issue to make
an OBS-package for the new devices that are going
to use a lot of .ko modules out of kernel source tree.
Change-Id: Ib200a3654368c58bd0da7db6daf0ba11be5c2b38
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
|
|
Change-Id: I207fc6c65d8174c7c75cc933d2ef45e2429bac00
Signed-off-by: Jinhyung Jo <jinhyung.jo@samsung.com>
|
|
This ioctl adds support of hardware surface convertion. Only y-invert
operation has been implemented so far.
Change-Id: Icf06dc84fd995eaa43c7990778d67e558c2c0274
Signed-off-by: Vladislav Andresov <v.andresov@partner.samsung.com>
Signed-off-by: Vasiliy Ulyanov <v.ulyanov@samsung.com>
|
|
The ioctl is needed to make ga_copy. Formely it was issued
from userspace using an execbuffer but currently it is done
directly via drmIoctl.
Aditionally it was necessary to import a device-specific
header. It has been placed to
include/uapi/drm/sdp_drm.h
like in device kernel. The header needs to be updated
whenever the original one is changed.
Change-Id: I6d78309f38b971d5d7014b1972ff2316eee27003
Signed-off-by: Vasiliy Ulyanov <v.ulyanov@samsung.com>
(cherry picked from commit 48b87ee9c5f0b41e96ab0b70c00a88adc8c26648)
|
|
Kernel devel package is used now to build modules out-of-tree
Change-Id: I70164fae7971270b5a38274a636c67dffa627162
Signed-off-by: Alexander Aksenov <a.aksenov@samsung.com>
|
|
|
|
Change-Id: I041f3d12de44ef1ec1b09b4d6f79820ab749cd97
Signed-off-by: Jinhyung Jo <jinhyung.jo@samsung.com>
|
|
TTM BUGs if ttm_tt appears bound while being swaped out. Certain
precautions are now taken in swap_notify ttm_bo_driver callback.
Change-Id: I0c461e6d179af4b424125c1615f95738ac429d47
Signed-off-by: Vasiliy Ulyanov <v.ulyanov@samsung.com>
(cherry picked from commit c1d6b3e728436abaf4833abc66be8bf0f299506f)
|