From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,pmladek@suse.com,feng.tang@linux.alibaba.com,include@grrlz.net,akpm@linux-foundation.org
Subject: [to-be-updated] panic-stop-cpus-that-lose-the-panic_redirect_cpu-race.patch removed from -mm tree
Date: Wed, 08 Jul 2026 20:13:02 -0700 [thread overview]
Message-ID: <20260709031302.B299E1F000E9@smtp.kernel.org> (raw)
The quilt patch titled
Subject: panic: stop CPUs that lose the panic_redirect_cpu race
has been removed from the -mm tree. Its filename was
panic-stop-cpus-that-lose-the-panic_redirect_cpu-race.patch
This patch was dropped because an updated version will be issued
------------------------------------------------------
From: Bradley Morgan <include@grrlz.net>
Subject: panic: stop CPUs that lose the panic_redirect_cpu race
Date: Tue, 7 Jul 2026 18:32:53 +0000
Loser of the redirect cmpxchg must stop, not fall through to
panic_try_start().
This issue was found by sashiko [1].
Link: https://lore.kernel.org/20260707183253.9793-1-include@grrlz.net
Link: https://sashiko.dev/#/patchset/20260705164123.18746-1-include%40grrlz.net [1]
Signed-off-by: Bradley Morgan <include@grrlz.net>
Cc: Petr Mladek <pmladek@suse.com>
Cc: Feng Tang <feng.tang@linux.alibaba.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/panic.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
--- a/kernel/panic.c~panic-stop-cpus-that-lose-the-panic_redirect_cpu-race
+++ a/kernel/panic.c
@@ -400,12 +400,9 @@ static bool panic_try_force_cpu(const ch
if (panic_in_progress())
return false;
- /*
- * Only one CPU can do the redirect. Use atomic cmpxchg to ensure
- * we don't race with another CPU also trying to redirect.
- */
+ /* Which CPU won the race? */
if (!atomic_try_cmpxchg(&panic_redirect_cpu, &old_cpu, this_cpu))
- return false;
+ return old_cpu != this_cpu;
/*
* Use dynamically allocated buffer if available, otherwise
_
Patches currently in -mm which might be from include@grrlz.net are
lib-string-fix-memchr_inv-for-large-ranges.patch
signal-avoid-shared-siginfo-namespace-rewrites.patch
panic-fix-va_list-reuse-in-panic_try_force_cpu.patch
reboot-use-lookup-tables-for-sysfs-mode-and-type-strings.patch
reboot-use-a-lookup-table-for-hw_protection_action-strings.patch
panic-make-force_cpu-redirect-work-from-an-nmi.patch
reply other threads:[~2026-07-09 3:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260709031302.B299E1F000E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.com \
--cc=include@grrlz.net \
--cc=mm-commits@vger.kernel.org \
--cc=pmladek@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.