From: Bradley Morgan <include@grrlz.net>
To: Petr Mladek <pmladek@suse.com>,
Feng Tang <feng.tang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jinchao Wang <wangjinchao600@gmail.com>,
Kees Cook <kees@kernel.org>, Rio <rioo.tsukatsukii@gmail.com>,
Joel Granados <joel.granados@kernel.org>,
Pnina Feder <pnina.feder@mobileye.com>,
Petr Pavlu <petr.pavlu@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Mayank Rungta <mrungta@google.com>, Tejun Heo <tj@kernel.org>,
Zhenguo Yao <yaozhenguo1@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Bradley Morgan <include@grrlz.net>
Subject: [PATCH v2 4/4] panic: avoid duplicate all CPU backtraces from sys_info
Date: Tue, 23 Jun 2026 15:35:01 +0000 [thread overview]
Message-ID: <2199a8b4da8700b9f27e61486293e9c26ab107ef.1782228656.git.include@grrlz.net> (raw)
In-Reply-To: <9b8c96e291696815d3c7de5d3e199298dee0279d.1782228656.git.include@grrlz.net>
panic_other_cpus_shutdown() handles SYS_INFO_ALL_BT before stopping the
other CPUs. Do not ask sys_info() to handle that bit again later in the
panic path.
Use sys_info_without_all_bt() so panic_print=all_bt does not request more
output after the CPUs are stopped.
Fixes: b76e89e50fc3 ("panic: generalize panic_print's function to show sys info")
Cc: stable@vger.kernel.org
Signed-off-by: Bradley Morgan <include@grrlz.net>
---
Changes since v1:
- New patch using the same helper for panic.
kernel/panic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/panic.c b/kernel/panic.c
index d030f88ad4ef..2cf229c7c0cf 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -683,7 +683,7 @@ void vpanic(const char *fmt, va_list args)
*/
atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
- sys_info(panic_print);
+ sys_info_without_all_bt(panic_print);
kmsg_dump_desc(KMSG_DUMP_PANIC, buf);
--
2.53.0
next prev parent reply other threads:[~2026-06-23 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 15:34 [PATCH v2 1/4] sys_info: add helper for callers that handle all_bt Bradley Morgan
2026-06-23 15:34 ` [PATCH v2 2/4] watchdog: avoid sys_info fallback for all_bt Bradley Morgan
2026-06-23 15:35 ` [PATCH v2 3/4] powerpc/watchdog: " Bradley Morgan
2026-06-23 15:35 ` Bradley Morgan [this message]
2026-06-23 20:11 ` [PATCH v2 1/4] sys_info: add helper for callers that handle all_bt Andy Shevchenko
2026-06-23 20:14 ` Andy Shevchenko
2026-06-23 20:16 ` 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=2199a8b4da8700b9f27e61486293e9c26ab107ef.1782228656.git.include@grrlz.net \
--to=include@grrlz.net \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chleroy@kernel.org \
--cc=dianders@chromium.org \
--cc=feng.tang@linux.alibaba.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mchauras@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=mrungta@google.com \
--cc=npiggin@gmail.com \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=pnina.feder@mobileye.com \
--cc=rioo.tsukatsukii@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=wangjinchao600@gmail.com \
--cc=yaozhenguo1@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