[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e94499dc-0155-0268-60a4-f9a11ad298a6@linux-m68k.org>
Date: Wed, 10 Sep 2025 16:40:53 +1000 (AEST)
From: Finn Thain <fthain@...ux-m68k.org>
To: Kent Overstreet <kent.overstreet@...ux.dev>
cc: Lance Yang <lance.yang@...ux.dev>, akpm@...ux-foundation.org,
amaindex@...look.com, anna.schumaker@...cle.com, boqun.feng@...il.com,
geert@...ux-m68k.org, 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, oak@...sinkinet.fi,
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 Tue, 9 Sep 2025, Kent Overstreet wrote:
> Err, I believe the topic was just alignment and the breaking of commonly
> held expectations :)
>
...
>
> Also, grep for READ_ONCE/WRITE_ONCE in the kernel tree if you want to
> see how big the issue is
I'm already aware of the comment in include/asm-generic/rwonce.h about
load tearing and 64-bit loads on 32-bit architectures. That's partly why I
mentioned long long alignment on i386. Perhaps, for being so common, i386
has generally lowered expectations?
Powered by blists - more mailing lists