tree 0b2cb0f3cf2852bf4138c13179221e58a37f402a
parent 01017a227044d64face2588fab9427a1da1bdb9f
author Nick Piggin <npiggin@suse.de> 1159520474 -0700
committer Linus Torvalds <torvalds@g5.osdl.org> 1159546701 -0700

[PATCH] oom: don't kill current when another OOM in progress

A previous patch to allow an exiting task to OOM kill itself (and thereby
avoid a little deadlock) introduced a problem.  We don't want the
PF_EXITING task, even if it is 'current', to access mem reserves if there
is already a TIF_MEMDIE process in the system sucking up reserves.

Also make the commenting a little bit clearer, and note that our current
scheme of effectively single threading the OOM killer is not itself
perfect.

Signed-off-by: Nick Piggin <npiggin@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>