Prev: [071/145] oprofile/x86: remove node check in AMD IBS initialization
Next: [040/145] net-sysfs: Use rtnl_trylock in wireless sysfs methods.
From: Greg KH on 12 Mar 2010 20:00 2.6.32-stable review patch. If anyone has any objections, please let me know. ---------------- From: KAMEZAWA Hiroyuki <kamezawa.hiroyu(a)jp.fujitsu.com> commit 5a2d41961dd6815b874b5c0afec0ac96cd90eea4 upstream. Presently the oom-killer is memcg aware and it finds the worst process from processes under memcg(s) in oom. Then, it kills victim's child first. It may kill a child in another cgroup and may not be any help for recovery. And it will break the assumption users have. This patch fixes it. Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu(a)jp.fujitsu.com> Reviewed-by: Minchan Kim <minchan.kim(a)gmail.com> Cc: Balbir Singh <balbir(a)linux.vnet.ibm.com> Reviewed-by: Daisuke Nishimura <nishimura(a)mxp.nes.nec.co.jp> Acked-by: David Rientjes <rientjes(a)google.com> Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh(a)suse.de> --- mm/oom_kill.c | 2 ++ 1 file changed, 2 insertions(+) --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -426,6 +426,8 @@ static int oom_kill_process(struct task_ list_for_each_entry(c, &p->children, sibling) { if (c->mm == p->mm) continue; + if (mem && !task_in_mem_cgroup(c, mem)) + continue; if (!oom_kill_task(c)) return 0; } -- 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/ |