[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6B2BA408B38BA1478B473C31C3D2074E30986F07FE@SV-EXCHANGE1.Corp.FC.LOCAL>
Date: Thu, 17 Apr 2014 08:03:10 -0700
From: Motohiro Kosaki <Motohiro.Kosaki@...fujitsu.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vivek Goyal <vgoyal@...hat.com>,
Eric Biederman <ebiederm@...ssion.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@...achi.com>,
Satoru MORIYA <satoru.moriya.br@...achi.com>,
Tomoki Sekiyama <tomoki.sekiyama@....com>
Subject: RE: [PATCH v2] kernel/panic: Add "crash_kexec_post_notifiers"
option for kdump after panic_notifers
> -----Original Message-----
> From: Masami Hiramatsu [mailto:masami.hiramatsu.pt@...achi.com]
> Sent: Wednesday, April 16, 2014 8:13 PM
> To: linux-kernel@...r.kernel.org; Vivek Goyal; Eric Biederman
> Cc: Andrew Morton; Yoshihiro YUNOMAE; Satoru MORIYA; Motohiro Kosaki; Tomoki Sekiyama
> Subject: [PATCH v2] kernel/panic: Add "crash_kexec_post_notifiers" option for kdump after panic_notifers
>
> Add a "crash_kexec_post_notifiers" option to run kdump after running panic_notifiers and dump kmsg. This can help rare situations
> which kdump drops in failure because of unstable crashed kernel or hardware failure (memory corruption on critical data/code), or
> the 2nd kernel is already broken by the 1st kernel (it's a broken behavior, but who can guarantee that the "crashed" kernel works
> correctly?).
>
> Usage: add "crash_kexec_post_notifiers" to kernel boot option.
>
> Note that this actually increases risks of the failure of kdump.
> This option should be set only if you worry about the rare case of kdump failure rather than increasing the chance of success.
>
> Changes from v1:
> - Rename late_kdump option to crash_kexec_post_notifiers.
> - Remove unneeded warning message.
>
> Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
> Cc: Eric Biederman <ebiederm@...ssion.com>
> Cc: Vivek Goyal <vgoyal@...hat.com>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Cc: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@...achi.com>
> Cc: Satoru MORIYA <satoru.moriya.br@...achi.com>
> Cc: Motohiro Kosaki <Motohiro.Kosaki@...fujitsu.com>
> Cc: Tomoki Sekiyama <tomoki.sekiyama@....com>
I have no objection.
Acked-by: KOSAKI Motohiro <Kosaki.motohiro@...fujitsu.com>
Powered by blists - more mailing lists