aboutsummaryrefslogtreecommitdiffstats
path: root/lib/debugobjects.c
diff options
context:
space:
mode:
authorMichal Hocko <[email protected]>2011-11-15 22:36:07 +0000
committerLinus Torvalds <[email protected]>2011-11-16 00:41:51 +0000
commit5aecc85abdb9ac2b0e6548d13652a34142e7ae89 (patch)
tree8939325e1ab98bce8caf16d9bdd3e57cd73af846 /lib/debugobjects.c
parentdrivers/misc/eeprom: fix dependecy on 'PPC_MPC5200_GPIO' (diff)
downloadkernel-5aecc85abdb9ac2b0e6548d13652a34142e7ae89.tar.gz
kernel-5aecc85abdb9ac2b0e6548d13652a34142e7ae89.zip
oom: do not kill tasks with oom_score_adj OOM_SCORE_ADJ_MIN
Commit c9f01245 ("oom: remove oom_disable_count") has removed the oom_disable_count counter which has been used for early break out from oom_badness so we could never select a task with oom_score_adj set to OOM_SCORE_ADJ_MIN (oom disabled). Now that the counter is gone we are always going through heuristics calculation and we always return a non zero positive value. This means that we can end up killing a task with OOM disabled because it is indistinguishable from regular tasks with 1% resp. CAP_SYS_ADMIN tasks with 3% usage of memory or tasks with oom_score_adj set but OOM enabled. Let's break out early if the task should have OOM disabled. Signed-off-by: Michal Hocko <[email protected]> Acked-by: David Rientjes <[email protected]> Acked-by: KOSAKI Motohiro <[email protected]> Cc: Oleg Nesterov <[email protected]> Cc: Ying Han <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions