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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2xhbtlynukbxhls4hfel2ctkrtzgivieqt2b5khbnduv6gqhbu@nfiks3nhnzcy>
Date: Sun, 25 Jan 2026 22:41:25 -0500
From: Aaron Tomlin <atomlin@...mlin.com>
To: Lance Yang <lance.yang@...ux.dev>
Cc: neelx@...e.com, sean@...e.io, pmladek@...e.com, 
	gregkh@...uxfoundation.org, joel.granados@...nel.org, mproche@...il.com, chjohnst@...il.com, 
	nick.lange@...il.com, linux-kernel@...r.kernel.org, mhiramat@...nel.org, 
	akpm@...ux-foundation.org
Subject: Re: [PATCH] hung_task: Differentiate between I/O and Lock/Resource
 waits

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

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)