From: Lance Yang <lance.yang@linux.dev>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: paulmck@kernel.org, john.ogness@linutronix.de,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Petr Mladek <pmladek@suse.com>, Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] generalize panic_print's dump function to be used by other kernel parts
Date: Thu, 3 Jul 2025 11:23:32 +0800 [thread overview]
Message-ID: <5f4f048e-02ff-4669-b4b1-e411c6be536b@linux.dev> (raw)
In-Reply-To: <20250703021004.42328-1-feng.tang@linux.alibaba.com>
Just hit a build failure with this patch series when building for arm64
with a minimal configuration:
kernel/panic.c: In function ‘setup_panic_sys_info’:
kernel/panic.c:151:23: error: implicit declaration of function
‘sys_info_parse_param’ [-Wimplicit-function-declaration]
151 | panic_print = sys_info_parse_param(buf);
| ^~~~~~~~~~~~~~~~~~~~
make[3]: *** [scripts/Makefile.build:287: kernel/panic.o] Error 1
make[2]: *** [scripts/Makefile.build:554: kernel] Error 2
To reproduce it:
$ make ARCH=arm64 allnoconfig
$ make ARCH=arm64 -j$(nproc)
Thanks,
Lance
On 2025/7/3 10:09, Feng Tang wrote:
> When working on kernel stability issues, panic, task-hung and
> software/hardware lockup are frequently met. And to debug them, user
> may need lots of system information at that time, like task call stacks,
> lock info, memory info etc.
>
> panic case already has panic_print_sys_info() for this purpose, and has
> a 'panic_print' bitmask to control what kinds of information is needed,
> which is also helpful to debug other task-hung and lockup cases.
>
> So this patchset extract the function out to a new file 'lib/sys_info.c',
> and make it available for other cases which also need to dump system info
> for debugging.
>
> Also as suggested by Petr Mladek, add 'panic_sys_info=' interface to
> take human readable string like "tasks,mem,locks,timers,ftrace,....",
> and eventually obsolete the current 'panic_print' bitmap interface.
>
> In RFC and V1 version, hung_task and SW/HW watchdog modules are enabled
> with the new sys_info dump interface. In v2, they are kept out for
> better review of current change, and will be posted later.
>
> Locally these have been used in our bug chasing for stability issues
> and was proven helpful.
>
> Many thanks to Petr Mladek for great suggestions on both the code and
> architectures!
>
> - Feng
>
> One to do left is about adding note for obsoleting 'panic_print' cmdline
> as discussed in https://lore.kernel.org/lkml/aFvBuOnD0cAEWJfl@U-2FWC9VHC-2323.local/
> and will be posted later.
>
> Changelog:
>
> Since v2:
> * Rename to PANIC_CONSOLE_REPLAY (Petr Mladek)
> * Don't let kernel.h include sys_info.h (Petr Mladek)
> * Improve documents and coding style (Petr Mladek/Lance Yang)
> * Add 'panic_console_replay' parameter (Petr Mladek)
> * Fix compiling problem (0Day bot)
> * Add reviewed-by tag from Petr for patch 1/5
>
> Since V1:
> * Separate the 'sys_show_info' related code to new file sys_info.[ch]
> (Petr Mladek)
> * Clean up the code for panic console replay (Petr Mladek)
> * Add 'panic_sys_info=' cmdline and sysctl interface for taking
> human readable parameters (Petr Mladek)
> * Add note about the obsoleting of 'panic_print' (Petr Mladek)
> * Hold the changes to hungtask/watchdog
>
> Since RFC:
> * Don't print all cpu backtrace if 'sysctl_hung_task_all_cpu_backtracemay'
> is 'false' (Lance Yang)
> * Change the name of 2 new kernel control knob to have 'mask' inside, and
> add kernel document and code comments for them (Lance Yang)
> * Make the sys_show_info() support printk msg replay and all CPU backtrace.
>
> Feng Tang (5):
> panic: clean up code for console replay
> panic: generalize panic_print's function to show sys info
> panic: add 'panic_sys_info' sysctl to take human readable string
> parameter
> panic: add 'panic_sys_info=' setup option for kernel cmdline
> panic: add note that panic_print sysctl interface is deprecated
>
> .../admin-guide/kernel-parameters.txt | 21 ++-
> Documentation/admin-guide/sysctl/kernel.rst | 20 ++-
> include/linux/sys_info.h | 27 ++++
> kernel/panic.c | 71 +++++-----
> lib/Makefile | 2 +-
> lib/sys_info.c | 122 ++++++++++++++++++
> 6 files changed, 221 insertions(+), 42 deletions(-)
> create mode 100644 include/linux/sys_info.h
> create mode 100644 lib/sys_info.c
>
next prev parent reply other threads:[~2025-07-03 3:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 2:09 Feng Tang
2025-07-03 2:10 ` [PATCH v3 1/5] panic: clean up code for console replay Feng Tang
2025-07-14 21:09 ` Askar Safin
2025-07-15 0:49 ` Feng Tang
2025-07-15 1:18 ` Askar Safin
2025-07-15 1:34 ` Feng Tang
2025-07-15 2:48 ` Askar Safin
2025-07-15 3:27 ` Feng Tang
2025-08-12 11:59 ` Petr Mladek
2025-08-13 0:43 ` Feng Tang
2025-07-03 2:10 ` [PATCH v3 2/5] panic: generalize panic_print's function to show sys info Feng Tang
2025-08-12 10:12 ` Petr Mladek
2025-07-03 2:10 ` [PATCH 3/5] panic: add 'panic_sys_info' sysctl to take human readable string parameter Feng Tang
2025-07-03 2:56 ` Lance Yang
2025-07-03 3:18 ` Feng Tang
2025-08-12 10:23 ` Petr Mladek
2025-08-13 0:39 ` Feng Tang
2025-07-03 2:10 ` [PATCH v3 4/5] panic: add 'panic_sys_info=' setup option for kernel cmdline Feng Tang
2025-08-12 10:31 ` Petr Mladek
2025-07-03 2:10 ` [PATCH v3 5/5] panic: add note that panic_print sysctl interface is deprecated Feng Tang
2025-08-12 11:52 ` Petr Mladek
2025-08-13 1:05 ` Feng Tang
2025-08-14 15:21 ` Petr Mladek
2025-07-03 3:23 ` Lance Yang [this message]
2025-07-03 4:56 ` [PATCH v3 0/5] generalize panic_print's dump function to be used by other kernel parts Lance Yang
2025-07-03 5:54 ` Feng Tang
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=5f4f048e-02ff-4669-b4b1-e411c6be536b@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=feng.tang@linux.alibaba.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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®