[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56784853-b653-4587-b850-b03359306366@linux.dev>
Date: Wed, 8 Oct 2025 11:03:18 +0800
From: Lance Yang <lance.yang@...ux.dev>
To: Finn Thain <fthain@...ux-m68k.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>, Eero Tamminen <oak@...sinkinet.fi>
Cc: 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 2025/10/8 08:40, Finn Thain wrote:
>
> On Tue, 7 Oct 2025, Andrew Morton wrote:
>
>>
>> Getting back to the $Subject at hand, are people OK with proceeding
>> with Lance's original fix?
>>
>
> Lance's patch is probably more appropriate for -stable than the patch I
> proposed -- assuming a fix is needed for -stable.
Thanks!
Apart from that, I believe this fix is still needed for the hung task
detector itself, to prevent unnecessary warnings in a few unexpected
cases.
>
> Besides those two alternatives, there is also a workaround:
> $ ./scripts/config -d DETECT_HUNG_TASK_BLOCKER
> which may be acceptable to the interested parties (i.e. m68k users).
>
> I don't have a preference. I'll leave it up to the bug reporters (Eero and
> Geert).
Powered by blists - more mailing lists