Nick Piggin b78483a4ba [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>
2006-09-29 09:18:21 -07:00
..
2006-09-26 08:48:44 -07:00
2006-01-11 18:42:13 -08:00
2006-07-03 15:27:07 -07:00
2006-09-26 08:48:45 -07:00
2006-09-26 08:48:58 -07:00
2005-04-16 15:20:36 -07:00
2006-06-26 18:35:02 +02:00
2006-09-26 08:48:44 -07:00
2006-09-29 09:18:10 -07:00
2006-09-26 08:48:45 -07:00
2006-08-27 11:01:28 -07:00
2006-09-27 08:26:12 -07:00
2006-09-27 08:26:12 -07:00