aboutsummaryrefslogtreecommitdiff
path: root/drivers/rtc/Kconfig
diff options
context:
space:
mode:
authorNick Piggin <npiggin@suse.de>2006-09-29 02:01:14 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2006-09-29 09:18:21 -0700
commitb78483a4ba60d5d90930262a533a784e1d9df660 (patch)
tree0b2cb0f3cf2852bf4138c13179221e58a37f402a /drivers/rtc/Kconfig
parent01017a227044d64face2588fab9427a1da1bdb9f (diff)
[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>
Diffstat (limited to 'drivers/rtc/Kconfig')
0 files changed, 0 insertions, 0 deletions