From: Bradley Morgan <brads@mainlining.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Petr Mladek <pmladek@suse.com>,
Jinchao Wang <wangjinchao600@gmail.com>,
Craig Lamparter <craig.lamparter@hpe.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Bradley Morgan <brads@mainlining.org>
Subject: [PATCH v7 0/6] panic: fix panic_force_cpu= redirect races and NMI bypass
Date: Wed, 16 Sep 2026 18:29:51 +0000 [thread overview]
Message-ID: <20260916182957.7788-1-brads@mainlining.org> (raw)
The panic_force_cpu= parameter redirects a panic to a specific CPU so
the crash kernel runs there. The redirect code in panic_try_force_cpu()
had two races and an NMI bypass, all found by Sashiko. This series
closes them and kills one more hack that the rework turned up.
Changes since v6, all from Petr's review:
Patch 4 now fixes the -Wformat-security warning that the __printf
annotation tripped in hpwdt, the closest caller: nmi_panic() there
passes a stack buffer, so it calls nmi_panic(regs, "%s", panic_msg)
now. The "every caller passes a plain string literal" claim is gone
from the changelog, it was wrong anyway, hpwdt never did. The
duplicate __printf annotation was dropped from the .c definition, the
header carries it.
Patch 6 dropped the "return value is not even checked" sentence from
the changelog. The kmalloc is gone entirely in this version, and the
self report on failure was deliberate anyway. The now constant msg
variable is gone too, panic_force_buf is passed directly.
Everything else is unchanged from v6. Patches 1, 2, 3 and 5 carry
Petr's Reviewed-by from the v6 thread. The double warning when a CPU
goes offline while marked in the panic mask and the set_cpu_online()
asymmetry in nmi_panic stay as they are, Petr called both not worth
touching. Rebased onto current master, the arch_do_panic rework from
Aug 31 merged cleanly on top.
Panic from NMI still goes through the redirect path first, so the
crash kernel ends up on the CPU the admin asked for. The redirect
buffer is a static 1KB now, no initcall, no fallback message.
Bradley Morgan (6):
panic: fix redirect CPU race in panic_try_force_cpu()
panic: flatten nmi_panic control flow
panic: fix va_list reuse in panic_try_force_cpu()
panic: restore variable arguments to nmi_panic()
panic: allow force_cpu redirect from an NMI
panic: kill the "buffer unavailable" redirect fallback
drivers/watchdog/hpwdt.c | 2 +-
include/linux/panic.h | 3 +-
kernel/panic.c | 80 ++++++++++++++++++++++------------------
3 files changed, 47 insertions(+), 38 deletions(-)
--
2.47.3
next reply other threads:[~2026-09-16 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 18:29 Bradley Morgan [this message]
2026-09-16 18:29 ` [PATCH v7 1/6] panic: fix redirect CPU race in panic_try_force_cpu() Bradley Morgan
2026-09-16 18:29 ` [PATCH v7 2/6] panic: flatten nmi_panic control flow Bradley Morgan
2026-09-16 18:29 ` [PATCH v7 3/6] panic: fix va_list reuse in panic_try_force_cpu() Bradley Morgan
2026-09-16 18:29 ` [PATCH v7 4/6] panic: restore variable arguments to nmi_panic() Bradley Morgan
2026-09-16 18:29 ` [PATCH v7 5/6] panic: allow force_cpu redirect from an NMI Bradley Morgan
2026-09-16 18:29 ` [PATCH v7 6/6] panic: kill the "buffer unavailable" redirect fallback Bradley Morgan
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=20260916182957.7788-1-brads@mainlining.org \
--to=brads@mainlining.org \
--cc=akpm@linux-foundation.org \
--cc=craig.lamparter@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pmladek@suse.com \
--cc=wangjinchao600@gmail.com \
--cc=wim@linux-watchdog.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
all inboxes | Powered by JetHome®