Prev: [tip:perf/core] perf, x86: Add Nehalem programming quirk to Westmere
Next: [GIT PULL][v2.6.34] tracing: fixes
From: David Rientjes on 2 Apr 2010 16:00 An oom_badness() score of 0 means "never kill" according to Documentation/filesystems/proc.txt, so explicitly exclude it from being selected for kill. These tasks have either detached their p->mm or are set to OOM_DISABLE. Signed-off-by: David Rientjes <rientjes(a)google.com> --- mm/oom_kill.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/mm/oom_kill.c b/mm/oom_kill.c --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -336,6 +336,8 @@ static struct task_struct *select_bad_process(unsigned int *ppoints, continue; points = oom_badness(p, totalpages); + if (!points) + continue; if (points > *ppoints || !chosen) { chosen = p; *ppoints = points; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |