From: Dave Young <dyoung@redhat.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, mcgrof@kernel.org,
keescook@chromium.org, yzaikin@google.com,
akpm@linux-foundation.org, feng.tang@intel.com,
siglesias@igalia.com, kernel@gpiccoli.net,
kexec@lists.infradead.org
Subject: Re: [PATCH 3/3] panic: Allow printing extra panic information on kdump
Date: Fri, 24 Dec 2021 09:35:12 +0800 [thread overview]
Message-ID: <YcUj0EJvQt77OVs2@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <2d24ea70-e315-beb5-0028-683880c438be@igalia.com>
Hi Guilherme,
On 12/22/21 at 09:34am, Guilherme G. Piccoli wrote:
> On 22/12/2021 08:45, Dave Young wrote:
> > Hi Guilherme,
> >
> > Thanks for you patch. Could you add kexec list for any following up
> > patches? This could change kdump behavior so let's see if any comments
> > from kexec list.
> >
> > Kudos for the lore+lei tool so that I can catch this by seeing this
> > coming into Andrews tree :)
>
> Hi Dave, I'm really sorry for not adding the kexec list, I forgot. But I
> will do next time for sure, my apologies. And thanks for taking a look
> after you noticed that on lore, I appreciate your feedback!
Thanks!
>
> > [...]
> > People may enable kdump crashkernel and panic_print together but
> > they are not aware the extra panic print could cause kdump not reliable
> > (in theory). So at least some words in kernel-parameters.txt would
> > help.
> >
>
> That makes sense, I'll improve that in a follow-up patch, how about
> that? Indeed it's a good idea to let people be sure that panic_print
> might affect kdump reliability, although I consider the risk to be
> pretty low. And I'll loop the kexec list for sure!
If only the doc update, I think it is fine to be another follup-up
patch.
About your 1st option in patch log, there is crash_kexec_post_notifiers
kernel param which can be used to switch on panic notifiers before kdump
bootup. Another way probably you can try to move panic print to be
panic notifier. Have this been discussed before?
>
> Cheers,
>
>
> Guilherme
Thanks
Dave
next prev parent reply other threads:[~2021-12-24 1:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 20:28 [PATCH 0/3] Some improvements on panic_print Guilherme G. Piccoli
2021-11-09 20:28 ` [PATCH 1/3] docs: sysctl/kernel: Add missing bit to panic_print Guilherme G. Piccoli
2021-11-30 5:09 ` Feng Tang
2021-11-09 20:28 ` [PATCH 2/3] panic: Add option to dump all CPUs backtraces in panic_print Guilherme G. Piccoli
2021-11-30 5:12 ` Feng Tang
2021-12-03 15:09 ` Guilherme G. Piccoli
2021-12-19 20:11 ` Luis Chamberlain
2021-12-20 12:38 ` Guilherme G. Piccoli
2021-12-21 23:48 ` Andrew Morton
2021-12-22 12:37 ` Guilherme G. Piccoli
2022-01-13 9:31 ` Petr Mladek
2021-11-09 20:28 ` [PATCH 3/3] panic: Allow printing extra panic information on kdump Guilherme G. Piccoli
2021-12-22 11:45 ` Dave Young
2021-12-22 12:34 ` Guilherme G. Piccoli
2021-12-24 1:35 ` Dave Young [this message]
2021-12-25 19:21 ` Guilherme G. Piccoli
2021-12-27 1:45 ` Dave Young
2021-12-27 3:14 ` Guilherme G. Piccoli
2022-01-13 9:02 ` Petr Mladek
2022-01-13 13:00 ` Guilherme G. Piccoli
2022-01-27 16:53 ` Guilherme G. Piccoli
2022-02-08 18:12 ` Guilherme G. Piccoli
2022-02-08 21:39 ` Stephen Rothwell
2022-02-09 15:06 ` Guilherme G. Piccoli
2022-02-09 23:26 ` Stephen Rothwell
2022-02-10 12:50 ` Guilherme G. Piccoli
2021-11-26 21:34 ` [PATCH 0/3] Some improvements on panic_print Guilherme G. Piccoli
2021-12-14 16:31 ` Guilherme G. Piccoli
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=YcUj0EJvQt77OVs2@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kernel@gpiccoli.net \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=siglesias@igalia.com \
--cc=yzaikin@google.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;
as well as URLs for NNTP newsgroup(s).