From: Baoquan He <bhe@redhat.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Hari Bathini <hbathini@linux.ibm.com>,
kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
Sachin P Bappalige <sachinpb@linux.vnet.ibm.com>
Subject: Re: [PATCH] kexec/crash: no crash update when kexec in progress
Date: Mon, 19 Aug 2024 14:15:52 +0800 [thread overview]
Message-ID: <ZsLjGJvAUIaxrG6x@MiWiFi-R3L-srv> (raw)
In-Reply-To: <355b58b1-6c51-4c42-b6ea-dcd6b1617a18@linux.ibm.com>
On 08/19/24 at 09:45am, Sourabh Jain wrote:
> Hello Michael and Boaquan
>
> On 01/08/24 12:21, Sourabh Jain wrote:
> > Hello Michael,
> >
> > On 01/08/24 08:04, Michael Ellerman wrote:
> > > Sourabh Jain <sourabhjain@linux.ibm.com> writes:
> > > > The following errors are observed when kexec is done with SMT=off on
> > > > powerpc.
> > > >
> > > > [ 358.458385] Removing IBM Power 842 compression device
> > > > [ 374.795734] kexec_core: Starting new kernel
> > > > [ 374.795748] kexec: Waking offline cpu 1.
> > > > [ 374.875695] crash hp: kexec_trylock() failed, elfcorehdr may
> > > > be inaccurate
> > > > [ 374.935833] kexec: Waking offline cpu 2.
> > > > [ 375.015664] crash hp: kexec_trylock() failed, elfcorehdr may
> > > > be inaccurate
> > > > snip..
> > > > [ 375.515823] kexec: Waking offline cpu 6.
> > > > [ 375.635667] crash hp: kexec_trylock() failed, elfcorehdr may
> > > > be inaccurate
> > > > [ 375.695836] kexec: Waking offline cpu 7.
> > > Are they actually errors though? Do they block the actual kexec from
> > > happening? Or are they just warnings in dmesg?
> >
> > The kexec kernel boots fine.
> >
> > This warning appears regardless of whether the kdump kernel is loaded.
> >
> > However, when the kdump kernel is loaded, we will not be able to update
> > the kdump image (FDT).
> > I think this should be fine given that kexec is in progress.
> >
> > Please let me know your opinion.
> >
> > > Because the fix looks like it could be racy.
> >
> > It seems like it is racy, but given that kexec takes the lock first and
> > then
> > brings the CPU up, which triggers the kdump image, which always fails to
> > update the kdump image because it could not take the same lock.
> >
> > Note: the kexec lock is not released unless kexec boot fails.
>
> Any comments or suggestions on this fix?
Is this a little better?
diff --git a/kernel/crash_core.c b/kernel/crash_core.c
index 63cf89393c6e..0355ffb712f4 100644
--- a/kernel/crash_core.c
+++ b/kernel/crash_core.c
@@ -504,7 +504,7 @@ int crash_check_hotplug_support(void)
crash_hotplug_lock();
/* Obtain lock while reading crash information */
- if (!kexec_trylock()) {
+ if (!kexec_trylock() && kexec_in_progress) {
pr_info("kexec_trylock() failed, elfcorehdr may be inaccurate\n");
crash_hotplug_unlock();
return 0;
@@ -539,7 +539,7 @@ static void crash_handle_hotplug_event(unsigned int hp_action, unsigned int cpu,
crash_hotplug_lock();
/* Obtain lock while changing crash information */
- if (!kexec_trylock()) {
+ if (!kexec_trylock() && kexec_in_progress) {
pr_info("kexec_trylock() failed, elfcorehdr may be inaccurate\n");
crash_hotplug_unlock();
return;
next prev parent reply other threads:[~2024-08-19 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240731152738.194893-1-sourabhjain@linux.ibm.com>
2024-08-01 2:34 ` [PATCH] kexec/crash: no crash update when kexec in progress Michael Ellerman
2024-08-01 6:51 ` Sourabh Jain
2024-08-19 4:15 ` Sourabh Jain
2024-08-19 6:15 ` Baoquan He [this message]
2024-08-20 6:40 ` Sourabh Jain
2024-08-30 11:17 ` Baoquan He
2024-09-04 9:25 ` Sourabh Jain
2024-09-05 3:23 ` Baoquan He
2024-09-05 8:37 ` Sourabh Jain
2024-09-08 10:30 ` Baoquan He
2024-09-09 5:05 ` Sourabh Jain
2024-09-09 5:23 ` Baoquan He
2024-09-09 5:31 ` Sourabh Jain
[not found] ` <Zqs8veRya7v/pXEt@MiWiFi-R3L-srv>
2024-08-01 8:06 ` Sourabh Jain
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=ZsLjGJvAUIaxrG6x@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sachinpb@linux.vnet.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=x86@kernel.org \
/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).