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

[Aaron Tomlin]

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

Attachment: signature.asc
Description: PGP signature