[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <efdd0d42567e4e7a94c8e5340ed4b35a@baidu.com>
Date: Thu, 25 Sep 2025 08:03:04 +0000
From: "Li,Rongqing" <lirongqing@...du.com>
To: Hillf Danton <hdanton@...a.com>
CC: LKML <linux-kernel@...r.kernel.org>
Subject: RE: [外部邮件] Re: [PATCH] hung_task: Panic after fixed number of hung tasks
> -----Original Message-----
> From: Hillf Danton <hdanton@...a.com>
> Sent: 2025年9月25日 15:37
> To: Li,Rongqing <lirongqing@...du.com>
> Cc: LKML <linux-kernel@...r.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@...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.
> >
> 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
Powered by blists - more mailing lists