From: Randy Dunlap <rdunlap@infradead.org>
To: lirongqing <lirongqing@baidu.com>,
corbet@lwn.net, akpm@linux-foundation.org, lance.yang@linux.dev,
mhiramat@kernel.org, paulmck@kernel.org,
pawan.kumar.gupta@linux.intel.com, mingo@kernel.org,
dave.hansen@linux.intel.com, rostedt@goodmis.org,
kees@kernel.org, arnd@arndb.de, feng.tang@linux.alibaba.com,
pauld@redhat.com, joel.granados@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v2] hung_task: Panic after fixed number of hung tasks
Date: Fri, 10 Oct 2025 17:25:05 -0700 [thread overview]
Message-ID: <d8c6762c-e08c-4b7a-92e9-7dad17ad0b49@infradead.org> (raw)
In-Reply-To: <20250928053137.3412-1-lirongqing@baidu.com>
Hi,
On 9/27/25 10:31 PM, lirongqing wrote:
> 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.
>
> Acked-by: Lance Yang <lance.yang@linux.dev>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> Diff with v1: change documentation as Lance suggested
>
> Documentation/admin-guide/sysctl/kernel.rst | 8 ++++++++
> kernel/hung_task.c | 14 +++++++++++++-
> 2 files changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index 8b49eab..98b47a7 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -405,6 +405,14 @@ This file shows up if ``CONFIG_DETECT_HUNG_TASK`` is enabled.
> 1 Panic immediately.
> = =================================================
>
> +hung_task_count_to_panic
> +=====================
The underline length should be at least as long as the title to
prevent kernel-doc build warnings. Same length is preferred.
> +
> +When set to a non-zero value, a kernel panic will be triggered if the
> +number of detected hung tasks reaches this value.
> +
> +Note that setting hung_task_panic=1 will still cause an immediate panic
> +on the first hung task.
>
> hung_task_check_count
> =====================
--
~Randy
next prev parent reply other threads:[~2025-10-11 0:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 5:31 lirongqing
2025-09-28 6:55 ` Lance Yang
2025-09-28 7:03 ` [外部邮件] " Li,Rongqing
2025-09-28 7:12 ` Lance Yang
2025-09-29 0:47 ` Masami Hiramatsu
2025-10-11 12:03 ` [????] " Li,Rongqing
2025-10-11 14:53 ` Li,Rongqing
2025-10-11 0:25 ` Randy Dunlap [this message]
2025-10-11 5:47 ` Kees Cook
2025-10-11 10:57 ` [外部邮件] " Li,Rongqing
2025-10-11 23:58 ` Li,Rongqing
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=d8c6762c-e08c-4b7a-92e9-7dad17ad0b49@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=feng.tang@linux.alibaba.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=pauld@redhat.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.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
all inboxes | Powered by JetHome®