From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754588Ab1G0M6r (ORCPT ); Wed, 27 Jul 2011 08:58:47 -0400 Received: from mtagate7.uk.ibm.com ([194.196.100.167]:50247 "EHLO mtagate7.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752213Ab1G0M6T (ORCPT ); Wed, 27 Jul 2011 08:58:19 -0400 Message-Id: <20110727125808.028895659@linux.vnet.ibm.com> User-Agent: quilt/0.48-1 Date: Wed, 27 Jul 2011 14:55:08 +0200 From: Michael Holzheu To: vgoyal@redhat.com Cc: ebiederm@xmission.com, mahesh@linux.vnet.ibm.com, hbabu@us.ibm.com, 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 Subject: [patch v2 04/10] kdump: Trigger kdump via panic notifier chain on s390 References: <20110727125504.491183728@linux.vnet.ibm.com> Content-Disposition: inline; filename=s390-kdump-common-shutdown-action.patch Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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);