linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: mhiramat@kernel.org, llong@redhat.com
Cc: Feng Tang <feng.tang@linux.alibaba.com>,
	Petr Mladek <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFC 0/3] generalize panic_print's dump function to be
Date: Fri, 9 May 2025 10:26:23 +0800	[thread overview]
Message-ID: <49efb43a-703e-495a-b076-dd386eb65e81@linux.dev> (raw)
In-Reply-To: <20250507104322.30700-1-feng.tang@linux.alibaba.com>

Cc Masami and Waiman

On 2025/5/7 18:43, 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, and make it usable for other
> cases which also need system info for debugging.
> 
> Locally these have been used in our bug chasing for stablility issues
> and was helpful.
> 
> Please help to review, thanks!
> 
> - Feng
> 
> Feng Tang (3):
>    kernel/panic: generalize panic_print's function to show sys info
>    kernel/hung_task: add option to dump system info when hung task
>      detected
>    kernel/watchdog: add option to dump system info when system is locked
>      up
> 
>   include/linux/panic.h | 12 ++++++++++++
>   kernel/hung_task.c    | 29 +++++++++++++++-------------
>   kernel/panic.c        | 44 +++++++++++++++++++++----------------------
>   kernel/watchdog.c     | 11 +++++++++++
>   4 files changed, 61 insertions(+), 35 deletions(-)
> 


      parent reply	other threads:[~2025-05-09  2:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 10:43 [PATCH RFC 0/3] generalize panic_print's dump function to be Feng Tang
2025-05-07 10:43 ` [PATCH RFC 1/3] kernel/panic: generalize panic_print's function to show sys info Feng Tang
2025-05-07 10:43 ` [PATCH RFC 2/3] kernel/hung_task: add option to dump system info when hung task detected Feng Tang
2025-05-08  3:02   ` Lance Yang
2025-05-08  5:45     ` Feng Tang
2025-05-09  4:44       ` Lance Yang
2025-05-09  6:35         ` Feng Tang
2025-05-07 10:43 ` [PATCH RFC 3/3] kernel/watchdog: add option to dump system info when system is locked up Feng Tang
2025-05-09  2:26 ` Lance Yang [this message]

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=49efb43a-703e-495a-b076-dd386eb65e81@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=feng.tang@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llong@redhat.com \
    --cc=mhiramat@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;
as well as URLs for NNTP newsgroup(s).