From: Jinchao Wang <wangjinchao600@gmail.com>
To: pmladek@suse.com, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, feng.tang@linux.alibaba.com,
joel.granados@kernel.org, john.ogness@linutronix.de,
wangjinchao600@gmail.com, namcao@linutronix.de,
sravankumarlpu@gmail.com
Subject: [PATCH 0/9] panic: introduce panic status function family
Date: Wed, 20 Aug 2025 17:14:45 +0800 [thread overview]
Message-ID: <20250820091702.512524-1-wangjinchao600@gmail.com> (raw)
This series introduces a family of helper functions
to manage panic state and updates existing code to
use them.
Before this series, panic state helpers were
scattered and inconsistent. For example,
panic_in_progress() was defined in printk/printk.c,
not in panic.c or panic.h. As a result, developers
had to look in unexpected places to understand or
re-use panic state logic. Other checks were open-
coded, duplicating logic across panic, crash, and
watchdog paths.
The new helpers centralize the functionality in
panic.c/panic.h:
- panic_try_start()
- panic_reset()
- panic_in_progress()
- panic_on_this_cpu()
- panic_on_other_cpu()
Patches 1–8 add the helpers and convert panic/crash
and printk/nbcon code to use them.
Patch 9 fixes a bug in the watchdog subsystem by
skipping checks when a panic is in progress, avoiding
interference with the panic CPU.
Together, this makes panic state handling simpler,
more discoverable, and more robust.
Jinchao Wang (9):
panic: Introduce helper functions for panic state
fbdev: Use panic_in_progress() helper
crash_core: use panic_try_start() in crash_kexec()
panic: use panic_try_start() in nmi_panic()
panic: use panic_try_start() in vpanic()
printk/nbcon: use panic_on_this_cpu() helper
panic/printk: replace this_cpu_in_panic() with panic_on_this_cpu()
panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu()
watchdog: skip checks when panic is in progress
drivers/video/fbdev/core/fbcon.c | 9 +---
include/linux/panic.h | 6 +++
include/linux/printk.h | 2 -
kernel/crash_core.c | 15 ++-----
kernel/panic.c | 71 +++++++++++++++++++++++++------
kernel/printk/internal.h | 1 -
kernel/printk/nbcon.c | 14 +++---
kernel/printk/printk.c | 37 +++-------------
kernel/printk/printk_ringbuffer.c | 2 +-
kernel/watchdog_buddy.c | 5 +++
kernel/watchdog_perf.c | 3 ++
lib/dump_stack.c | 2 +-
12 files changed, 89 insertions(+), 78 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-20 9:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 9:14 Jinchao Wang [this message]
2025-08-20 9:14 ` [PATCH 1/9] panic: Introduce helper functions for panic state Jinchao Wang
2025-08-20 9:14 ` [PATCH 2/9] fbdev: Use panic_in_progress() helper Jinchao Wang
2025-08-20 9:14 ` [PATCH 3/9] crash_core: use panic_try_start() in crash_kexec() Jinchao Wang
2025-08-20 9:14 ` [PATCH 4/9] panic: use panic_try_start() in nmi_panic() Jinchao Wang
2025-08-20 9:14 ` [PATCH 5/9] panic: use panic_try_start() in vpanic() Jinchao Wang
2025-08-20 9:14 ` [PATCH 6/9] printk/nbcon: use panic_on_this_cpu() helper Jinchao Wang
2025-08-20 9:14 ` [PATCH 7/9] panic/printk: replace this_cpu_in_panic() with panic_on_this_cpu() Jinchao Wang
2025-08-20 9:14 ` [PATCH 8/9] panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu() Jinchao Wang
2025-08-20 9:14 ` [PATCH 9/9] watchdog: skip checks when panic is in progress Jinchao Wang
2025-08-20 15:18 ` Yury Norov
2025-08-21 1:29 ` Jinchao Wang
2025-08-25 10:05 ` [PATCH 8/9] panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu() John Ogness
2025-08-25 9:53 ` [PATCH 6/9] printk/nbcon: use panic_on_this_cpu() helper John Ogness
2025-08-26 0:58 ` Jinchao Wang
2025-08-20 13:35 ` [PATCH 3/9] crash_core: use panic_try_start() in crash_kexec() Baoquan He
2025-08-20 13:43 ` Baoquan He
2025-08-21 2:43 ` Baoquan He
2025-08-21 3:41 ` Jinchao Wang
2025-08-20 10:44 ` [PATCH 2/9] fbdev: Use panic_in_progress() helper Qianqiang Liu
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=20250820091702.512524-1-wangjinchao600@gmail.com \
--to=wangjinchao600@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.com \
--cc=joel.granados@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=pmladek@suse.com \
--cc=sravankumarlpu@gmail.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).