Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932300Ab0BPADe (ORCPT ); Mon, 15 Feb 2010 19:03:34 -0500 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:53584 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756692Ab0BPADd (ORCPT ); Mon, 15 Feb 2010 19:03:33 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Tue, 16 Feb 2010 09:00:05 +0900 From: KAMEZAWA Hiroyuki To: David Rientjes Cc: Andrew Morton , Rik van Riel , Nick Piggin , Andrea Arcangeli , Balbir Singh , Lubos Lunak , KOSAKI Motohiro , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [patch -mm 4/9 v2] oom: remove compulsory panic_on_oom mode Message-Id: <20100216090005.f362f869.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: References: Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 2.7.1 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1107 Lines: 27 On Mon, 15 Feb 2010 14:20:09 -0800 (PST) David Rientjes wrote: > If /proc/sys/vm/panic_on_oom is set to 2, the kernel will panic > regardless of whether the memory allocation is constrained by either a > mempolicy or cpuset. > > Since mempolicy-constrained out of memory conditions now iterate through > the tasklist and select a task to kill, it is possible to panic the > machine if all tasks sharing the same mempolicy nodes (including those > with default policy, they may allocate anywhere) or cpuset mems have > /proc/pid/oom_adj values of OOM_DISABLE. This is functionally equivalent > to the compulsory panic_on_oom setting of 2, so the mode is removed. > > Signed-off-by: David Rientjes NACK. In an enviroment which depends on cluster-fail-over, this is useful even if in such situation. Thanks, -Kame -- 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/