From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ns2.suse.de ([195.135.220.15] helo=mx2.suse.de) by canuck.infradead.org with esmtps (Exim 4.63 #1 (Red Hat Linux)) id 1IE65s-0006qC-SW for kexec@lists.infradead.org; Thu, 26 Jul 2007 12:21:42 -0400 Date: Thu, 26 Jul 2007 18:21:34 +0200 From: Bernhard Walle Subject: Re: [patch] add kdump_after_notifier Message-ID: <20070726162134.GA13880@suse.de> References: <469F55D0.4050203@ah.jp.nec.com> <20070726140702.GA8949@suse.de> <20070726153240.GA15969@in.ibm.com> <20070726153440.GA19095@suse.de> <20070726154415.GB15969@in.ibm.com> <20070726154718.GA25561@suse.de> <20070726155444.GC15969@in.ibm.com> <20070726161431.GA32008@suse.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20070726161431.GA32008@suse.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org+dwmw2=infradead.org@lists.infradead.org To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Andrew Morton * Bernhard Walle [2007-07-26 18:14]: > * Vivek Goyal [2007-07-26 17:54]: > > > > That's true. Its not mainline. We had similar discussion in the past > > also. I think we should allow only audited code to be run after panic(). > > Leaving it open to modules or unaudited code makes this solution > > something like LKCD where whole lot of code used to run after the crash, > > hence was unreliable. > > > > If KDB goes mainline, then I think it is not a bad idea to call debugger > > first (if it is enabled) and then one can trigger crash dump from inside > > the debugger. > > Well, after thinking again about this, I think the best solution would > to call kdump from KDB with a command as it was done by LKCD. Ok, but that doesn't solve the problem (it would solve the opposite problem). My question is: Why cannot kdump use the notifier call chain? Wouldn't this simplify things in general, apart from KDB. Not talking about the priority of kdump now ... Thanks, Bernhard _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec