From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-Id: <20110704170959.733121710@linux.vnet.ibm.com> Date: Mon, 04 Jul 2011 19:09:29 +0200 From: Michael Holzheu Subject: [patch 7/9] kdump: Trigger kdump via panic notifier chain on s390 References: <20110704170922.976299676@linux.vnet.ibm.com> Content-Disposition: inline; filename=07-s390-kdump-common-shutdown-action.patch Sender: linux-kernel-owner@vger.kernel.org List-Archive: List-Post: To: ebiederm@xmission.com, vgoyal@redhat.com, hbabu@us.ibm.com, mahesh@linux.vnet.ibm.com Cc: oomichi@mxs.nes.nec.co.jp, horms@verge.net.au, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org List-ID: From: Michael Holzheu On s390 we have the possibility to configure actions that are executed in case of a kernel panic. E.g. it is possible to automatically trigger an s390 stand-alone dump. The actions are called via a panic notifier. We also want to trigger kdump via the notifier call chain. Therefore this patch disables for s390 the direct kdump invocation in the panic() function. Signed-off-by: Michael Holzheu --- kernel/panic.c | 3 +++ 1 file changed, 3 insertions(+) --- a/kernel/panic.c +++ b/kernel/panic.c @@ -84,9 +84,12 @@ NORET_TYPE void panic(const char * fmt, /* * If we have crashed and we have a crash kernel loaded let it handle * everything else. + * For s390 kdump is triggered via the panic notifier call chain. * Do we want to call this before we try to display a message? */ +#if !defined(CONFIG_S390) crash_kexec(NULL); +#endif kmsg_dump(KMSG_DUMP_PANIC);