aboutsummaryrefslogtreecommitdiffstats
path: root/arch/cris
diff options
context:
space:
mode:
authorMichal Hocko <mhocko@suse.cz>2011-11-15 14:36:07 -0800
committerZiyan <jaraidaniel@gmail.com>2015-01-15 20:49:23 +0100
commit8c2f0c19455340fd12c9b806385679b42db07b38 (patch)
tree1294985f5781e624e8e30c7581782d3b82e43ddf /arch/cris
parentdf23f40df4094a46d879be61e7d0a1f2da929972 (diff)
downloadkernel_samsung_tuna-8c2f0c19455340fd12c9b806385679b42db07b38.zip
kernel_samsung_tuna-8c2f0c19455340fd12c9b806385679b42db07b38.tar.gz
kernel_samsung_tuna-8c2f0c19455340fd12c9b806385679b42db07b38.tar.bz2
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 <mhocko@suse.cz> Acked-by: David Rientjes <rientjes@google.com> Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Cc: Oleg Nesterov <oleg@redhat.com> Cc: Ying Han <yinghan@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/cris')
0 files changed, 0 insertions, 0 deletions