From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932140AbXDRE4F (ORCPT ); Wed, 18 Apr 2007 00:56:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753707AbXDRE4F (ORCPT ); Wed, 18 Apr 2007 00:56:05 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:55172 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753774AbXDRE4E (ORCPT ); Wed, 18 Apr 2007 00:56:04 -0400 Date: Tue, 17 Apr 2007 21:56:02 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Yasunori Goto cc: Larry Woodman , Linux Kernel Mailing List Subject: Re: [PATCH] sysctl_panic_on_oom broken In-Reply-To: <20070418104631.EE4A.Y-GOTO@jp.fujitsu.com> Message-ID: References: <462515CC.1080107@redhat.com> <20070418104631.EE4A.Y-GOTO@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 18 Apr 2007, Yasunori Goto wrote: > If panic_on_oom is 1, only panic if mempolicy/cpuset is not used. > And if panic_on_oom is 2, panic on all case. > This might be desirable. Sounds good. Add some documentation mentioned that this may panic your system if there is still plenty of memory available.