Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754866AbYCPXd1 (ORCPT ); Sun, 16 Mar 2008 19:33:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752858AbYCPXdT (ORCPT ); Sun, 16 Mar 2008 19:33:19 -0400 Received: from mx1.redhat.com ([66.187.233.31]:32799 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752546AbYCPXdT (ORCPT ); Sun, 16 Mar 2008 19:33:19 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Oleg Nesterov X-Fcc: ~/Mail/linus Cc: Andrew Morton , Davide Libenzi , "Eric W. Biederman" , Ingo Molnar , Laurent Riffard , Pavel Emelyanov , linux-kernel@vger.kernel.org Subject: Re: [PATCH 4/5] don't panic if /sbin/init exits or killed In-Reply-To: Oleg Nesterov's message of Monday, 17 March 2008 02:03:46 +0300 <20080316230346.GA379@tv-sign.ru> References: <20080316155453.GA20845@tv-sign.ru> <20080316221938.D217026F995@magilla.localdomain> <20080316230346.GA379@tv-sign.ru> X-Shopping-List: (1) Mountainous symmetrical digression digressions (2) Geopolitical faceers (3) Spacious cackling whips (4) Injured negligent ghost-melt lesions Message-Id: <20080316233242.DC9E226F995@magilla.localdomain> Date: Sun, 16 Mar 2008 16:32:42 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1258 Lines: 31 > But panic() isn't better? It doesn't provide any useful info. It is not misleading in the same way. It's clear that going to look at the kernel source is not the place to find the root of the problem. > Well, I think the generic "if we have a chance to survive, we should try > to survive" rule is good. > > If the boot init dies, at least the admin has a chance to figure out what > has happened, and -o remount,ro /. For me and you, I agree. I think the common case is that there is no admin prepared to do any such thing, but just someone expecting a reboot to fix things and preferring that a failing system reboot itself in the middle of the night rather than wedge. > Every BUG/BUG_ON in fact means the system is not useable, but still it does > not panic(), but tries to proceed. Many production systems probably set panic_on_oops. Having the init panic behavior keyed on that seems fine to me. I just don't like the "kernel bug at this source line" output when it's not true. Thanks, Roland -- 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/