linux-kernel - Re: [外部邮件] Re: [PATCH][v2] hung_task: Panic after fixed number of hung tasks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1f7483f8-29bb-4caa-8978-2bdad0d46072@linux.dev>
Date: Sun, 28 Sep 2025 15:12:03 +0800
From: Lance Yang <lance.yang@...ux.dev>
To: "Li,Rongqing" <lirongqing@...du.com>,
 "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
 "mhiramat@...nel.org" <mhiramat@...nel.org>
Cc: "corbet@....net" <corbet@....net>, "mingo@...nel.org" <mingo@...nel.org>,
 "pauld@...hat.com" <pauld@...hat.com>,
 "joel.granados@...nel.org" <joel.granados@...nel.org>,
 "arnd@...db.de" <arnd@...db.de>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
 "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
 "feng.tang@...ux.alibaba.com" <feng.tang@...ux.alibaba.com>,
 "kees@...nel.org" <kees@...nel.org>, "paulmck@...nel.org"
 <paulmck@...nel.org>,
 "pawan.kumar.gupta@...ux.intel.com" <pawan.kumar.gupta@...ux.intel.com>,
 "rostedt@...dmis.org" <rostedt@...dmis.org>
Subject: Re: [外部邮件] Re: [PATCH][v2] hung_task: Panic after fixed number of hung tasks



On 2025/9/28 15:03, Li,Rongqing wrote:
>> On 2025/9/28 13:31, lirongqing wrote:
>>> From: Li RongQing <lirongqing@...du.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.
>>>
>>> Acked-by: Lance Yang <lance.yang@...ux.dev>
>>> Signed-off-by: Li RongQing <lirongqing@...du.com>
>>> ---
>>
>> It's working as expect. So:
>> Tested-by: Lance Yang <lance.yang@...ux.dev>
>>
>> But on second thought: regarding this new sysctl parameter, I was wondering if
>> a name like max_hung_task_count_to_panic might be a bit more explicit, just to
>> follow the convention from max_rcu_stall_to_panic.
>>
> 
> I see that all the hung task sysctl parameters start with "hung_task"? Should we keep this convention? If so, we could name it "hung_task_max_to_panic". If not, we could call it "max_hang_task_to_panic"?

Well, let's see what other folks think ;)