From: Will Deacon <will@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>, Marco Elver <elver@google.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Waiman Long <longman@redhat.com>,
Bart Van Assche <bvanassche@acm.org>,
llvm@lists.linux.dev, David Laight <david.laight.linux@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Nathan Chancellor <nathan@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@kernel.org>,
Boqun Feng <boqun@kernel.org>
Subject: Re: [PATCH v4 0/2] arm64: Fixes for __READ_ONCE() with CONFIG_LTO=y
Date: Fri, 27 Feb 2026 03:16:31 +0000 [thread overview]
Message-ID: <177212898809.385801.8626009504655274507.b4-ty@kernel.org> (raw)
In-Reply-To: <20260216142436.2207937-2-elver@google.com>
On Mon, 16 Feb 2026 15:16:21 +0100, Marco Elver wrote:
> While investigating a Clang Context Analysis [1] false positive [2], I
> started to dig deeper into arm64's __READ_ONCE() implementation with
> LTO. That rabbit hole led me to find one critical bug with the current
> implementation (fixed already in [3]), and subtle improvements that then
> enabled me to fix the original false positive.
>
> Patch 1 refactors the macro to use a different way of getting an
> unqualified type and eliminates the ternary conditional.
>
> [...]
Applied to arm64 (for-next/read-once), thanks!
[1/2] arm64: Optimize __READ_ONCE() with CONFIG_LTO=y
https://git.kernel.org/arm64/c/abf1be684dc2
[2/2] arm64, compiler-context-analysis: Permit alias analysis through __READ_ONCE() with CONFIG_LTO=y
https://git.kernel.org/arm64/c/773b24bcedc1
Peter -- please don't pull this just yet. I'd like it to get some
exposure to the various build bots and CI systems in case of any nasty
toolchain interactions.
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-02-27 3:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 14:16 Marco Elver
2026-02-16 14:16 ` [PATCH v4 1/2] arm64: Optimize " Marco Elver
2026-02-16 14:16 ` [PATCH v4 2/2] arm64, compiler-context-analysis: Permit alias analysis through " Marco Elver
2026-02-16 18:00 ` David Laight
2026-02-16 18:40 ` Marco Elver
2026-02-27 3:16 ` Will Deacon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177212898809.385801.8626009504655274507.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=boqun@kernel.org \
--cc=bvanassche@acm.org \
--cc=catalin.marinas@arm.com \
--cc=david.laight.linux@gmail.com \
--cc=elver@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®