From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Baoquan He <bhe@redhat.com>, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, pmladek@suse.com, anton@enomsg.org,
ccross@android.com, dyoung@redhat.com, feng.tang@intel.com,
john.ogness@linutronix.de, keescook@chromium.org,
kernel@gpiccoli.net, kexec@lists.infradead.org,
rostedt@goodmis.org, senozhatsky@chromium.org,
tony.luck@intel.com, vgoyal@redhat.com
Subject: Re: [PATCH V4] panic: Move panic_print before kmsg dumpers
Date: Thu, 27 Jan 2022 13:47:34 -0300 [thread overview]
Message-ID: <7b93afff-66a0-44ee-3bb7-3d1e12dd47c2@igalia.com> (raw)
In-Reply-To: <20220126052246.GC2086@MiWiFi-R3L-srv>
On 26/01/2022 02:22, Baoquan He wrote:
> [...]
>> if (!_crash_kexec_post_notifiers) {
>> + if (kexec_crash_loaded())
>> + panic_print_sys_info(false);
>> +
>
> Please reconsider this change. As I said in another thread, it's not
> suggested when adding any action before kdump switching and the action
> doesn't benefit kdump switching.
>
> We don't oppose execute handling before kdump switching as long as
> it's executed conditionally. For those conditional extra handling and
> the followoing crash dumping's stability, it's not under kdump's care.
>
Hi Baoquan, thanks for your review - I understand your concern, so let's
reconsider the change, as you suggest. The only thing is that the
specific bit that concerns you is not really a code added by the hereby
proposed patch, but it was in another patch I submitted, that reached
linux-next.
So, Andrew : can I ask you to please remove the following patch from
linux-next?
"panic: allow printing extra panic information on kdump"
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=56439cb78293
(I'll also send this request in the original thread of the patch, for
completeness).
Baoquan: once it's removed from linux-next, I'll rework this proposed
patch and send a V5, hopefully a version that you consider more safe =)
Cheers,
Guilherme
prev parent reply other threads:[~2022-01-27 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 20:31 Guilherme G. Piccoli
2022-01-26 5:22 ` Baoquan He
2022-01-27 16:47 ` Guilherme G. Piccoli [this message]
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=7b93afff-66a0-44ee-3bb7-3d1e12dd47c2@igalia.com \
--to=gpiccoli@igalia.com \
--cc=akpm@linux-foundation.org \
--cc=anton@enomsg.org \
--cc=bhe@redhat.com \
--cc=ccross@android.com \
--cc=dyoung@redhat.com \
--cc=feng.tang@intel.com \
--cc=john.ogness@linutronix.de \
--cc=keescook@chromium.org \
--cc=kernel@gpiccoli.net \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tony.luck@intel.com \
--cc=vgoyal@redhat.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
all inboxes | Powered by JetHome®