From: "Li,Rongqing" <lirongqing@baidu.com>
To: Lance Yang <lance.yang@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
David Hildenbrand <david@redhat.com>,
Florian Wesphal <fw@strlen.de>, Jakub Kacinski <kuba@kernel.org>,
"Jason A . Donenfeld" <jason@zx2c4.com>,
Joel Granados <joel.granados@kernel.org>,
Joel Stanley <joel@jms.id.au>, Jonathan Corbet <corbet@lwn.net>,
Kees Cook <kees@kernel.org>,
Liam Howlett <liam.howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Petr Mladek <pmladek@suse.com>, "Phil Auld" <pauld@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Russell King <linux@armlinux.org.uk>,
Shuah Khan <shuah@kernel.org>, Simon Horman <horms@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Steven Rostedt <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [外部邮件] Re: [PATCH][v4] hung_task: Panic when there are more than N hung tasks at the same time
Date: Thu, 16 Oct 2025 05:57:34 +0000 [thread overview]
Message-ID: <bb443552b6db40548a4fae98d1f63c80@baidu.com> (raw)
In-Reply-To: <4db3bd26-1f74-4096-84fd-f652ec9a4d27@linux.dev>
> LGTM. It works as expected, thanks!
>
> On 2025/10/15 14:36, lirongqing wrote:
> > From: Li RongQing <lirongqing@baidu.com>
>
> For the commit message, I'd suggest the following for better clarity:
>
> ```
> The hung_task_panic sysctl is currently a blunt instrument: it's all or nothing.
>
> Panicking on a single hung task can be an overreaction to a transient glitch. A
> more reliable indicator of a systemic problem is when multiple tasks hang
> simultaneously.
>
> Extend hung_task_panic to accept an integer threshold, allowing the kernel
> to panic only when N hung tasks are detected in a single scan. This provides
> finer control to distinguish between isolated incidents and system-wide
> failures.
>
> The accepted values are:
> - 0: Don't panic (unchanged)
> - 1: Panic on the first hung task (unchanged)
> - N > 1: Panic after N hung tasks are detected in a single scan
>
> The original behavior is preserved for values 0 and 1, maintaining full
> backward compatibility.
> ```
>
> If you agree, likely no need to resend - Andrew could pick it up directly when
> applying :)
>
This is better;
Andrew, could you pick it up directly
Thanks
-Li
> >
> > Currently, when 'hung_task_panic' is enabled, the kernel panics
> > immediately upon detecting the first hung task. However, some hung
> > tasks are transient and allow system recovery, while persistent hangs
> > should trigger a panic when accumulating beyond a threshold.
> >
> > Extend the 'hung_task_panic' sysctl to accept a threshold value
> > specifying the number of hung tasks that must be detected before
> > triggering a kernel panic. This provides finer control for
> > environments where transient hangs may occur but persistent hangs
> should be fatal.
> >
> > The sysctl now accepts:
> > - 0: don't panic (maintains original behavior)
> > - 1: panic on first hung task (maintains original behavior)
> > - N > 1: panic after N hung tasks are detected in a single scan
> >
> > This maintains backward compatibility while providing flexibility for
> > different hang scenarios.
> >
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> > Cc: Andrew Jeffery <andrew@codeconstruct.com.au>
> > Cc: Anshuman Khandual <anshuman.khandual@arm.com>
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: David Hildenbrand <david@redhat.com>
> > Cc: Florian Wesphal <fw@strlen.de>
> > Cc: Jakub Kacinski <kuba@kernel.org>
> > Cc: Jason A. Donenfeld <jason@zx2c4.com>
> > Cc: Joel Granados <joel.granados@kernel.org>
> > Cc: Joel Stanley <joel@jms.id.au>
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: Kees Cook <kees@kernel.org>
> > Cc: Lance Yang <lance.yang@linux.dev>
> > Cc: Liam Howlett <liam.howlett@oracle.com>
> > Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
> > Cc: "Paul E . McKenney" <paulmck@kernel.org>
> > Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> > Cc: Petr Mladek <pmladek@suse.com>
> > Cc: Phil Auld <pauld@redhat.com>
> > Cc: Randy Dunlap <rdunlap@infradead.org>
> > Cc: Russell King <linux@armlinux.org.uk>
> > Cc: Shuah Khan <shuah@kernel.org>
> > Cc: Simon Horman <horms@kernel.org>
> > Cc: Stanislav Fomichev <sdf@fomichev.me>
> > Cc: Steven Rostedt <rostedt@goodmis.org>
> > ---
>
> So:
>
> Reviewed-by: Lance Yang <lance.yang@linux.dev>
> Tested-by: Lance Yang <lance.yang@linux.dev>
>
> Cheers,
> Lance
next prev parent reply other threads:[~2025-11-19 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 6:36 [PATCH][v4] hung_task: Panic when there are more than N hung tasks at the same time lirongqing
2025-10-16 5:07 ` Lance Yang
2025-10-16 5:57 ` Li,Rongqing [this message]
2025-10-16 20:50 ` [外部邮件] " Andrew Morton
2025-10-16 8:02 ` Masami Hiramatsu
2025-10-16 12:47 ` Paul Menzel
2025-10-17 2:09 ` [外部邮件] " Li,Rongqing
2025-10-17 5:17 ` Andrew Jeffery
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=bb443552b6db40548a4fae98d1f63c80@baidu.com \
--to=lirongqing@baidu.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@codeconstruct.com.au \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=jason@zx2c4.com \
--cc=joel.granados@kernel.org \
--cc=joel@jms.id.au \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam.howlett@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pauld@redhat.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=wireguard@lists.zx2c4.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