summaryrefslogtreecommitdiffstats
path: root/Documentation/i2c/fault-codes
diff options
context:
space:
mode:
authorMichal Hocko <mhocko@suse.com>2016-07-29 00:45:19 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2016-07-29 01:07:41 +0200
commitfec1e5f987bfc41f9f08cbd206e7302e6ac2ab0c (patch)
tree3135e0abb28984ed05862f6c1b5d3865251aa0da /Documentation/i2c/fault-codes
parentfreezer, oom: check TIF_MEMDIE on the correct task (diff)
downloadlinux-fec1e5f987bfc41f9f08cbd206e7302e6ac2ab0c.tar.xz
linux-fec1e5f987bfc41f9f08cbd206e7302e6ac2ab0c.zip
cpuset, mm: fix TIF_MEMDIE check in cpuset_change_task_nodemask
Commit c0ff7453bb5c ("cpuset,mm: fix no node to alloc memory when changing cpuset's mems") has added TIF_MEMDIE and PF_EXITING check but it is checking the flag on the current task rather than the given one. This doesn't make much sense and it is actually wrong. If the current task which updates the nodemask of a cpuset got killed by the OOM killer then a part of the cpuset cgroup processes would have incompatible nodemask which is surprising to say the least. The comment suggests the intention was to skip oom victim or an exiting task so we should be checking the given task. But even then it would be layering violation because it is the memory allocator to interpret the TIF_MEMDIE meaning. Simply drop both checks. All tasks in the cpuset should simply follow the same mask. Link: http://lkml.kernel.org/r/1467029719-17602-3-git-send-email-mhocko@kernel.org Signed-off-by: Michal Hocko <mhocko@suse.com> Cc: David Rientjes <rientjes@google.com> Cc: Miao Xie <miaox@cn.fujitsu.com> Cc: Miao Xie <miaoxie@huawei.com> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/i2c/fault-codes')
0 files changed, 0 insertions, 0 deletions