From: "Li,Rongqing" <lirongqing@baidu.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Lance Yang <lance.yang@linux.dev>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
David Hildenbrand <david@redhat.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
Stanislav Fomichev <sdf@fomichev.me>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>,
"Russell King" <linux@armlinux.org.uk>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Shuah Khan <shuah@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
"Jonathan Corbet" <corbet@lwn.net>,
Joel Granados <joel.granados@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
Phil Auld <pauld@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
"Pawan Gupta" <pawan.kumar.gupta@linux.intel.com>,
Simon Horman <horms@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Florian Westphal <fw@strlen.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Kees Cook <kees@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Feng Tang <feng.tang@linux.alibaba.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>
Subject: RE: [????] Re: [????] Re: [PATCH][v3] hung_task: Panic after fixed number of hung tasks
Date: Wed, 15 Oct 2025 02:04:21 +0000 [thread overview]
Message-ID: <b7937a55047b44c687e11e219a62009e@baidu.com> (raw)
In-Reply-To: <aO5Ldv4U8QSGgfog@pathway.suse.cz>
> I would also update the subject to something like:
>
> hung_task: Panic when there are more than N hung tasks at the same
> time
>
Ok, I will update
>
>
> That said, I think that both approaches make sense.
>
> Your approach would trigger the panic when many processes are stuck.
> Note that it still might be a transient state. But I agree that the more stuck
> processes exist the more serious the problem likely is for the heath of the
> system.
>
> My approach would trigger panic when a single process hangs for a long
> time. It will trigger more likely only when the problem is persistent. The
> seriousness depends on which particular process get stuck.
>
Yes, both are reasonable requirement, and I will leave it to you or anyone else interested to implement it
Thanks
-Li.
> I am fine with your approach. Just please, make more clear that the number
> means the number of hung tasks at the same time.
> And mention the problems to login, ...
>
> Best Regards,
> Petr
next prev parent reply other threads:[~2025-10-15 2:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-12 11:50 [PATCH][v3] hung_task: Panic after fixed number of hung tasks lirongqing
2025-10-12 13:26 ` [PATCH v3] " Markus Elfring
2025-10-13 2:14 ` [外部邮件] " Li,Rongqing
2025-10-14 1:37 ` [PATCH][v3] " Randy Dunlap
2025-10-14 5:23 ` Lance Yang
2025-10-14 9:45 ` Petr Mladek
2025-10-14 10:49 ` [????] " Li,Rongqing
2025-10-14 13:09 ` Petr Mladek
2025-10-15 2:04 ` Li,Rongqing [this message]
2025-10-14 10:59 ` Lance Yang
2025-10-14 11:18 ` [外部邮件] " Li,Rongqing
2025-10-14 11:40 ` Lance Yang
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=b7937a55047b44c687e11e219a62009e@baidu.com \
--to=lirongqing@baidu.com \
--cc=Jason@zx2c4.com \
--cc=Liam.Howlett@oracle.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=feng.tang@linux.alibaba.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=joel.granados@kernel.org \
--cc=joel@jms.id.au \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=lance.yang@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).