linux-kernel - Re: [PATCH v3] hung_task: Explicitly report I/O wait state in log output

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: <btdi6lgza4a4uspdq6zo554naajst7qtgp3fpjf7u43om6srb2@m7h34ce3jnci>
Date: Tue, 10 Feb 2026 08:19:26 -0500
From: Aaron Tomlin <atomlin@...mlin.com>
To: Petr Mladek <pmladek@...e.com>
Cc: akpm@...ux-foundation.org, lance.yang@...ux.dev, mhiramat@...nel.org, 
	gregkh@...uxfoundation.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 v3] hung_task: Explicitly report I/O wait state in log
 output

On Tue, Feb 10, 2026 at 10:40:40AM +0100, Petr Mladek wrote:
> If you really want to write something about the possible race
> then I would write something like:
> 
>   Theoretically, io_schedule_finish() could be called in parallel
>   and the read flag need not match the later printed backtrace.
>   It should be acceptable in practice. The entire report is
>   racy. And it works most of the time, especially because
>   long stalls are being reported. And adding any extra
>   synchronization seems entirely disproportionate in this
>   scenario.
> 
Hi Petr,

Thank you. This is acceptable.

Hi Andrew,

Would you mind replacing the last paragraph of the current commit message
with the version above? I believe it would be pertinent to include the race
condition, notwithstanding khungtaskd by design.

Kind regards,
-- 
Aaron Tomlin

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