From: Lance Yang <lance.yang@linux.dev>
To: "Li,Rongqing" <lirongqing@baidu.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"paulmck@kernel.org" <paulmck@kernel.org>,
"pawan.kumar.gupta@linux.intel.com"
<pawan.kumar.gupta@linux.intel.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"kees@kernel.org" <kees@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"feng.tang@linux.alibaba.com" <feng.tang@linux.alibaba.com>,
"pauld@redhat.com" <pauld@redhat.com>,
"joel.granados@kernel.org" <joel.granados@kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [外部邮件] Re: [PATCH][RFC] hung_task: Support to panic when the maximum number of hung task warnings is reached
Date: Tue, 23 Sep 2025 13:55:20 +0800 [thread overview]
Message-ID: <06facb7b-7d1b-44fd-b530-9a5300db7d4c@linux.dev> (raw)
In-Reply-To: <bbdc2b5c2b374ed1801113148a72d83c@baidu.com>
On 2025/9/23 13:22, Li,Rongqing wrote:
>>> I assume the same argument applies to the NMI watchdog, to the
>>> softlockup detector and to the RCU stall detector?
>>>
>>> A general framework to handle all of these might be better. But why
>>> do it in kernel at all? What about a userspace detector which parses
>>> kernel logs (or new procfs counters) and makes such decisions?
>>
>> +1. I agree that a userspace detector seems more appropriate for this.
>>
>
> I think the user-space maybe flexibility, but incurs relatively higher overhead and is less reliable. When the system hangs, this task may have already hung as well.
Emmm... if the system is so degraded that a userspace monitor cannot get
scheduled, it's very likely that khungtaskd itself is also struggling to
run, right?
>
>
>> We already have the hung_task_detect_count counter, so a userspace detector
>> could easily use that to implement custom policies ;)
next prev parent reply other threads:[~2025-09-23 5:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 3:37 [PATCH][RFC] hung_task: Support to panic when the maximum number of hung task warnings is reached lirongqing
2025-09-23 3:45 ` Andrew Morton
2025-09-23 3:59 ` Lance Yang
2025-09-23 5:22 ` [外部邮件] " Li,Rongqing
2025-09-23 5:55 ` Lance Yang [this message]
2025-09-23 6:19 ` Li,Rongqing
2025-09-23 4:00 ` [????] " Li,Rongqing
2025-09-23 6:03 ` Paul E. McKenney
2025-09-23 6:16 ` [外部邮件] " Li,Rongqing
2025-09-23 7:01 ` Li,Rongqing
2025-09-23 4:35 ` Randy Dunlap
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=06facb7b-7d1b-44fd-b530-9a5300db7d4c@linux.dev \
--to=lance.yang@linux.dev \
--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=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;
as well as URLs for NNTP newsgroup(s).