[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3b2ap3n6qpimqwgu3zvjlob5jipchglfdyvgj5xn337rlzz6ut@dykb5goxdgeb>
Date: Wed, 28 Jan 2026 14:13:18 -0500
From: Aaron Tomlin <atomlin@...mlin.com>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: akpm@...ux-foundation.org, lance.yang@...ux.dev,
gregkh@...uxfoundation.org, pmladek@...e.com, joel.granados@...nel.org, neelx@...e.com,
sean@...e.io, mproche@...il.com, chjohnst@...il.com, nick.lange@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hung_task: Differentiate between I/O and Lock/Resource
waits
On Wed, Jan 28, 2026 at 05:17:49PM +0900, Masami Hiramatsu wrote:
> If this is only for human readability, I rather like just adding
> "in iowait" at the end. "D" state seems redundant, and "Lock/Resource"
> can mislead. What about something like below?
>
> pr_err("INFO: task %s:%d blocked for more than %ld seconds%s.\n",
> ..., t->in_iowait ? " in I/O wait" : "");
>
Hi Masami,
Thank you for your feedback.
I concur. I'll incorporate the suggestion.
Kind regards,
--
Aaron Tomlin
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists