From: Vivek Goyal <vgoyal@redhat.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: linux-kernel@vger.kernel.org,
Satoru MORIYA <satoru.moriya.br@hitachi.com>,
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>,
Takenori Nagano <t-nagano@ah.jp.nec.com>,
Eric Biederman <ebiederm@xmission.com>,
Motohiro Kosaki <Motohiro.Kosaki@us.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kernel/panic: Add "late_kdump" option for kdump in unstable condition
Date: Thu, 17 Apr 2014 09:43:38 -0400 [thread overview]
Message-ID: <20140417134338.GB15749@redhat.com> (raw)
In-Reply-To: <534F3572.2040801@hitachi.com>
On Thu, Apr 17, 2014 at 10:59:14AM +0900, Masami Hiramatsu wrote:
[..]
> >> @@ -112,9 +113,14 @@ void panic(const char *fmt, ...)
> >> /*
> >> * If we have crashed and we have a crash kernel loaded let it handle
> >> * everything else.
> >> - * Do we want to call this before we try to display a message?
> >> + * If we want to call this after we try to display a message, pass
> >> + * the "late_kdump" option to the kernel.
> >> */
> >> - crash_kexec(NULL);
> >> + if (!late_kdump)
> >> + crash_kexec(NULL);
> >> + else
> >> + pr_emerg("Warning: late_kdump option is set. Please DO NOT "
> >> + "report bugs about kdump failure with this option.\n");
> >
> > I think above message about DO NOT report bugs seems unnecessary.
>
> OK, so I just notify the option is set as below.
> "Warning: crash_kexec_post_notifiers is set.\n"
I would say for the time being don't put any extra message. User will
think what this warning is supposed to mean. We can introduce one if
we run into many issues.
For the time being we can just look at kernel logs and look at command
line options and see whether crash_kexec_post_notifiers was set or not.
Thanks
Vivek
next prev parent reply other threads:[~2014-04-17 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 4:51 [PATCH] kernel/panic: Add "late_kdump" option for kdump in unstable condition Masami Hiramatsu
2014-04-14 5:14 ` Eric W. Biederman
2014-04-14 6:13 ` Masami Hiramatsu
2014-04-14 12:48 ` Vivek Goyal
2014-04-14 19:31 ` Vivek Goyal
2014-04-15 1:37 ` Masami Hiramatsu
2014-04-15 14:08 ` Vivek Goyal
2014-04-16 1:28 ` Masami Hiramatsu
2014-04-16 2:33 ` Vivek Goyal
2014-04-16 4:50 ` Masami Hiramatsu
2014-04-16 13:48 ` Vivek Goyal
2014-04-17 1:59 ` Masami Hiramatsu
2014-04-17 13:43 ` Vivek Goyal [this message]
2014-04-18 3:09 ` Masami Hiramatsu
2014-04-21 0:59 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140417134338.GB15749@redhat.com \
--to=vgoyal@redhat.com \
--cc=Motohiro.Kosaki@us.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=satoru.moriya.br@hitachi.com \
--cc=t-nagano@ah.jp.nec.com \
--cc=yoshihiro.yunomae.ez@hitachi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox