linux-kernel - Re: [PATCH v2 1/1] hung_task: fix warnings caused by unaligned lock pointers

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ba00388c-1d5b-4d95-054d-a6f09af41e7b@linux-m68k.org>
Date: Wed, 8 Oct 2025 21:12:24 +1100 (AEDT)
From: Finn Thain <fthain@...ux-m68k.org>
To: Lance Yang <lance.yang@...ux.dev>
cc: Andrew Morton <akpm@...ux-foundation.org>, 
    Geert Uytterhoeven <geert@...ux-m68k.org>, 
    Eero Tamminen <oak@...sinkinet.fi>, 
    Kent Overstreet <kent.overstreet@...ux.dev>, amaindex@...look.com, 
    anna.schumaker@...cle.com, boqun.feng@...il.com, ioworker0@...il.com, 
    joel.granados@...nel.org, jstultz@...gle.com, leonylgao@...cent.com, 
    linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org, 
    longman@...hat.com, mhiramat@...nel.org, mingo@...hat.com, 
    mingzhe.yang@...com, peterz@...radead.org, rostedt@...dmis.org, 
    senozhatsky@...omium.org, tfiga@...omium.org, will@...nel.org, 
    stable@...r.kernel.org
Subject: Re: [PATCH v2 1/1] hung_task: fix warnings caused by unaligned lock
 pointers


On Wed, 8 Oct 2025, Lance Yang wrote:

> 
> In other words, we are not just fixing the bug reported by Eero and 
> Geert, but correcting the blocker tracking mechanism's flawed assumption 
> for -stable ;)
> 
> If you feel this doesn't qualify as a fix, I can change the Fixes: tag 
> to point to the original commit that introduced this flawed mechanism 
> instead.
> 

That's really a question for the bug reporters. I don't personally have a 
problem with CONFIG_DETECT_HUNG_TASK_BLOCKER so I can't say whether the 
fix meets the requirements set in 
Documentation/process/stable-kernel-rules.rst. And I still don't know 
what's meant by "unnecessary warnings in a few unexpected cases".