[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250724151035.cc2d421d1b1ed20b89be1917@linux-foundation.org>
Date: Thu, 24 Jul 2025 15:10:35 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Lance Yang <lance.yang@...ux.dev>
Cc: Ye Liu <ye.liu@...ux.dev>, Ye Liu <liuye@...inos.cn>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] hung_task: Add detection count to hung task warning
message
On Thu, 24 Jul 2025 20:06:52 +0800 Lance Yang <lance.yang@...ux.dev> wrote:
>
>
> On 2025/7/24 15:23, Ye Liu wrote:
> > From: Ye Liu <liuye@...inos.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".
Powered by blists - more mailing lists