Re: [PATCH] hung_task: Differentiate between I/O and Lock/Resource waits

[Aaron Tomlin]

On Mon, Jan 26, 2026 at 10:30:22AM +0800, Lance Yang wrote:
> Why do we need this?
> 
> It's rather obvious that the stack trace already shows whether it
> is in "D (Disk I/O)" or "D (Lock/Resource)" or "D (...)".

Hi Lance,

Thank you for your review.

While I agree that a seasoned kernel developer can often deduce the root
cause by inspecting the stack trace, this level of analysis is not always
immediately accessible to some system administrators or first-line support
engineers.

The primary benefit of this patch is to provide high-level clarity at a
glance.

By explicitly distinguishing between "Disk I/O" and "Lock/Resource"
contention in the initial log message, we allow some administrators or
support engineers to rapidly route the incident to the appropriate team
(e.g., storage/network vs. kernel etc.) without needing to parse or
understand the nuances of kernel stack traces.


Kind regards,
-- 
Aaron Tomlin

Attachment: signature.asc
Description: PGP signature