From: "Li,Rongqing" <lirongqing@baidu.com>
To: Hillf Danton <hdanton@sina.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: RE: [外部邮件] Re: [PATCH] hung_task: Panic after fixed number of hung tasks
Date: Thu, 25 Sep 2025 08:03:04 +0000 [thread overview]
Message-ID: <efdd0d42567e4e7a94c8e5340ed4b35a@baidu.com> (raw)
In-Reply-To: <20250925073717.7636-1-hdanton@sina.com>
> -----Original Message-----
> From: Hillf Danton <hdanton@sina.com>
> Sent: 2025年9月25日 15:37
> To: Li,Rongqing <lirongqing@baidu.com>
> Cc: LKML <linux-kernel@vger.kernel.org>
> Subject: [外部邮件] Re: [PATCH] hung_task: Panic after fixed number of hung
> tasks
>
> On Thu, 25 Sep 2025 14:06:05 +0800
> > From: Li RongQing <lirongqing@baidu.com>
> >
> > Currently, when hung_task_panic is enabled, kernel will panic
> > immediately upon detecting the first hung task. However, some hung
> > tasks are transient and the system can recover fully, while others are
> > unrecoverable and trigger consecutive hung task reports, and a panic is
> expected.
> >
> > This commit adds a new sysctl parameter hung_task_count_to_panic to
> > allows specifying the number of consecutive hung tasks that must be
> > detected before triggering a kernel panic. This provides finer control
> > for environments where transient hangs maybe happen but persistent
> > hangs should still be fatal.
> >
> Given transient, bumping sysctl_hung_task_timeout_secs up alone helps.
However, this will prevent the printing of hung task warnings. Hung task warnings are
very useful for identifying which tasks are hanging and where they are stuck.
If there is hung_task_count_to_panic, I hope to shorten sysctl_hung_task_timeout_secs to give more information.
Thanks
next prev parent reply other threads:[~2025-09-25 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 6:06 [PATCH] hung_task: Panic after fixed number of hung tasks lirongqing
2025-09-25 7:37 ` Hillf Danton
2025-09-25 8:03 ` Li,Rongqing [this message]
2025-09-25 10:26 ` Lance Yang
2025-09-26 18:02 ` Paul E. McKenney
2025-09-27 2:18 ` Lance Yang
2025-09-28 1:51 ` [????] " Li,Rongqing
2025-09-27 2:39 ` Lance Yang
2025-09-28 1:54 ` [外部邮件] " Li,Rongqing
2025-09-28 3:19 ` Li,Rongqing
2025-09-28 3:29 ` Lance Yang
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=efdd0d42567e4e7a94c8e5340ed4b35a@baidu.com \
--to=lirongqing@baidu.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.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