summaryrefslogtreecommitdiffstats
path: root/mm/vmscan.c
diff options
context:
space:
mode:
authorDavid Rientjes2014-08-07 01:07:58 +0200
committerLinus Torvalds2014-08-07 03:01:21 +0200
commitfb794bcbb4e5552242f9a4c5e1ffe4c6da29a968 (patch)
tree00365c507d5dd171ef18ac0341f49564c1637c57 /mm/vmscan.c
parentmm: fix potential infinite loop in dissolve_free_huge_pages() (diff)
downloadkernel-qcow2-linux-fb794bcbb4e5552242f9a4c5e1ffe4c6da29a968.tar.gz
kernel-qcow2-linux-fb794bcbb4e5552242f9a4c5e1ffe4c6da29a968.tar.xz
kernel-qcow2-linux-fb794bcbb4e5552242f9a4c5e1ffe4c6da29a968.zip
mm, oom: remove unnecessary exit_state check
The oom killer scans each process and determines whether it is eligible for oom kill or whether the oom killer should abort because of concurrent memory freeing. It will abort when an eligible process is found to have TIF_MEMDIE set, meaning it has already been oom killed and we're waiting for it to exit. Processes with task->mm == NULL should not be considered because they are either kthreads or have already detached their memory and killing them would not lead to memory freeing. That memory is only freed after exit_mm() has returned, however, and not when task->mm is first set to NULL. Clear TIF_MEMDIE after exit_mm()'s mmput() so that an oom killed process is no longer considered for oom kill, but only until exit_mm() has returned. This was fragile in the past because it relied on exit_notify() to be reached before no longer considering TIF_MEMDIE processes. Signed-off-by: David Rientjes <rientjes@google.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>
Diffstat (limited to 'mm/vmscan.c')
0 files changed, 0 insertions, 0 deletions