* [PATCH v2] hung_task: Add detection count to hung task warning message
@ 2025-07-24 7:23 Ye Liu
2025-07-24 12:06 ` Lance Yang
0 siblings, 1 reply; 4+ messages in thread
From: Ye Liu @ 2025-07-24 7:23 UTC (permalink / raw)
To: Andrew Morton; +Cc: Ye Liu, Lance Yang, linux-kernel
From: Ye Liu <liuye@kylinos.cn>
Add [#N] to hung task warnings to show occurrence count.
This helps quickly identify warning order when multiple
messages appear in logs.
Signed-off-by: Ye Liu <liuye@kylinos.cn>
Changes in v2:
- Directly use sysctl_hung_task_detect_count.
- Link to v1:https://lore.kernel.org/all/20250721031755.1418556-1-ye.liu@linux.dev/
---
kernel/hung_task.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/kernel/hung_task.c b/kernel/hung_task.c
index 8708a1205f82..231afdb68bb2 100644
--- a/kernel/hung_task.c
+++ b/kernel/hung_task.c
@@ -232,8 +232,9 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout)
if (sysctl_hung_task_warnings || hung_task_call_panic) {
if (sysctl_hung_task_warnings > 0)
sysctl_hung_task_warnings--;
- pr_err("INFO: task %s:%d blocked for more than %ld seconds.\n",
- t->comm, t->pid, (jiffies - t->last_switch_time) / HZ);
+ pr_err("INFO: task %s:%d blocked for more than %ld seconds. [#%ld]\n",
+ t->comm, t->pid, (jiffies - t->last_switch_time) / HZ,
+ sysctl_hung_task_detect_count);
pr_err(" %s %s %.*s\n",
print_tainted(), init_utsname()->release,
(int)strcspn(init_utsname()->version, " "),
--
2.43.0
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v2] hung_task: Add detection count to hung task warning message
2025-07-24 7:23 [PATCH v2] hung_task: Add detection count to hung task warning message Ye Liu
@ 2025-07-24 12:06 ` Lance Yang
2025-07-24 22:10 ` Andrew Morton
0 siblings, 1 reply; 4+ messages in thread
From: Lance Yang @ 2025-07-24 12:06 UTC (permalink / raw)
To: Ye Liu, Andrew Morton; +Cc: Ye Liu, linux-kernel
On 2025/7/24 15:23, Ye Liu wrote:
> From: Ye Liu <liuye@kylinos.cn>
>
> Add [#N] to hung task warnings to show occurrence count.
> This helps quickly identify warning order when multiple
> messages appear in logs.
Hmm... once we have this number, what do we do with it?
While I totally get the desire for a quick reference number, my thinking
is that the hung_task_detect_count counter is the intended and more
reliable way for users to check.
But like I said before, let's see what Andrew thinks ;)
Thanks,
Lance
>
> Signed-off-by: Ye Liu <liuye@kylinos.cn>
>
> Changes in v2:
> - Directly use sysctl_hung_task_detect_count.
> - Link to v1:https://lore.kernel.org/all/20250721031755.1418556-1-ye.liu@linux.dev/
> ---
> kernel/hung_task.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/hung_task.c b/kernel/hung_task.c
> index 8708a1205f82..231afdb68bb2 100644
> --- a/kernel/hung_task.c
> +++ b/kernel/hung_task.c
> @@ -232,8 +232,9 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout)
> if (sysctl_hung_task_warnings || hung_task_call_panic) {
> if (sysctl_hung_task_warnings > 0)
> sysctl_hung_task_warnings--;
> - pr_err("INFO: task %s:%d blocked for more than %ld seconds.\n",
> - t->comm, t->pid, (jiffies - t->last_switch_time) / HZ);
> + pr_err("INFO: task %s:%d blocked for more than %ld seconds. [#%ld]\n",
> + t->comm, t->pid, (jiffies - t->last_switch_time) / HZ,
> + sysctl_hung_task_detect_count);
> pr_err(" %s %s %.*s\n",
> print_tainted(), init_utsname()->release,
> (int)strcspn(init_utsname()->version, " "),
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2] hung_task: Add detection count to hung task warning message
2025-07-24 12:06 ` Lance Yang
@ 2025-07-24 22:10 ` Andrew Morton
2025-07-25 2:24 ` Lance Yang
0 siblings, 1 reply; 4+ messages in thread
From: Andrew Morton @ 2025-07-24 22:10 UTC (permalink / raw)
To: Lance Yang; +Cc: Ye Liu, Ye Liu, linux-kernel
On Thu, 24 Jul 2025 20:06:52 +0800 Lance Yang <lance.yang@linux.dev> wrote:
>
>
> On 2025/7/24 15:23, Ye Liu wrote:
> > From: Ye Liu <liuye@kylinos.cn>
> >
> > Add [#N] to hung task warnings to show occurrence count.
> > This helps quickly identify warning order when multiple
> > messages appear in logs.
>
> Hmm... once we have this number, what do we do with it?
Yes, adding to the changelog a more comprehensive description of the
use-cases would help get this patch into Linux.
> While I totally get the desire for a quick reference number, my thinking
> is that the hung_task_detect_count counter is the intended and more
> reliable way for users to check.
But that's what this patch does? Confused.
> But like I said before, let's see what Andrew thinks ;)
Andrew thinks it's a pain when the title of a patch is changed!
Fortunately the changelog had a "Link to v1".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2] hung_task: Add detection count to hung task warning message
2025-07-24 22:10 ` Andrew Morton
@ 2025-07-25 2:24 ` Lance Yang
0 siblings, 0 replies; 4+ messages in thread
From: Lance Yang @ 2025-07-25 2:24 UTC (permalink / raw)
To: Andrew Morton, Ye Liu; +Cc: Ye Liu, linux-kernel
On 2025/7/25 06:10, Andrew Morton wrote:
> On Thu, 24 Jul 2025 20:06:52 +0800 Lance Yang <lance.yang@linux.dev> wrote:
>
>>
>>
>> On 2025/7/24 15:23, Ye Liu wrote:
>>> From: Ye Liu <liuye@kylinos.cn>
>>>
>>> Add [#N] to hung task warnings to show occurrence count.
>>> This helps quickly identify warning order when multiple
>>> messages appear in logs.
>>
>> Hmm... once we have this number, what do we do with it?
>
> Yes, adding to the changelog a more comprehensive description of the
> use-cases would help get this patch into Linux.
Yep, exactly. Please sell this change to us! A good changelog should
explain not just what the patch does, but why it's necessary ;p
>
>> While I totally get the desire for a quick reference number, my thinking
>> is that the hung_task_detect_count counter is the intended and more
>> reliable way for users to check.
>
> But that's what this patch does? Confused.
I'm just not sure if this quick reference number is something users
actually need, as there doesn't seem to be a strong use-case for it yet.
My point was that actively checking the sysctl is the proper way to get the
total count. But of course, if users genuinely need this inline number, I
have no objection ;)
>
>> But like I said before, let's see what Andrew thinks ;)
>
> Andrew thinks it's a pain when the title of a patch is changed!
> Fortunately the changelog had a "Link to v1".
https://lore.kernel.org/lkml/20250721031755.1418556-1-ye.liu@linux.dev/
Thanks,
Lance
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-07-25 2:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-24 7:23 [PATCH v2] hung_task: Add detection count to hung task warning message Ye Liu
2025-07-24 12:06 ` Lance Yang
2025-07-24 22:10 ` Andrew Morton
2025-07-25 2:24 ` Lance Yang
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).