Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754648Ab0F3J0F (ORCPT ); Wed, 30 Jun 2010 05:26:05 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:50571 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554Ab0F3J0B (ORCPT ); Wed, 30 Jun 2010 05:26:01 -0400 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 From: KOSAKI Motohiro To: LKML , linux-mm , Andrew Morton , Minchan Kim , David Rientjes , KAMEZAWA Hiroyuki Subject: [mmotm 0611][PATCH 00/11] various OOM bugfixes v3 Cc: kosaki.motohiro@jp.fujitsu.com Message-Id: <20100630172430.AA42.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.50.07 [ja] Date: Wed, 30 Jun 2010 18:25:58 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1157 Lines: 30 Hi Here is updated series for various OOM fixes. Almost fixes are trivial. One big improvement is Luis's dying task priority boost patch. This is necessary for RT folks. oom: don't try to kill oom_unkillable child oom: oom_kill_process() doesn't select kthread child oom: make oom_unkillable_task() helper function oom: oom_kill_process() need to check p is unkillable oom: /proc//oom_score treat kernel thread honestly oom: kill duplicate OOM_DISABLE check oom: move OOM_DISABLE check from oom_kill_task to out_of_memory() oom: cleanup has_intersects_mems_allowed() oom: remove child->mm check from oom_kill_process() oom: give the dying task a higher priority oom: multi threaded process coredump don't make deadlock fs/proc/base.c | 5 ++- mm/oom_kill.c | 100 +++++++++++++++++++++++++++++++++++++++----------------- 2 files changed, 73 insertions(+), 32 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/