From: Will Deacon <will@kernel.org>
To: "Catalin Marinas" <catalin.marinas@arm.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andy Lutomirski" <luto@kernel.org>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
John Stultz <jstultz@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: uapi: Provide correct __BITS_PER_LONG for the compat vDSO
Date: Mon, 8 Sep 2025 16:55:32 +0100 [thread overview]
Message-ID: <175734490190.158300.1463560749148120421.b4-ty@kernel.org> (raw)
In-Reply-To: <20250821-vdso-arm64-compat-bitsperlong-v1-0-700bcabe7732@linutronix.de>
On Thu, 21 Aug 2025 09:56:43 +0200, Thomas Weißschuh wrote:
> The generic vDSO library uses the UAPI headers. On arm64 __BITS_PER_LONG is
> always '64' even when used from the compat vDSO. In that case __GENMASK()
> does an illegal bitshift, invoking undefined behaviour.
>
> The first patch should go into the 6.17 tree.
>
>
> [...]
Applied to arm64 (for-next/vdso), thanks!
[2/3] arm64: vdso32: Stop suppressing warnings
https://git.kernel.org/arm64/c/80c4e1948908
[3/3] arm64: vdso32: Respect -Werror from kbuild
https://git.kernel.org/arm64/c/281817dffe28
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-09-08 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 7:56 Thomas Weißschuh
2025-08-21 7:56 ` [PATCH 1/3] " Thomas Weißschuh
2025-08-21 17:09 ` John Stultz
2025-08-21 17:33 ` Arnd Bergmann
2025-08-21 7:56 ` [PATCH 2/3] arm64: vdso32: Stop suppressing warnings Thomas Weißschuh
2025-08-21 7:56 ` [PATCH 3/3] arm64: vdso32: Respect -Werror from kbuild Thomas Weißschuh
2025-09-03 10:49 ` [PATCH 0/3] arm64: uapi: Provide correct __BITS_PER_LONG for the compat vDSO Thomas Weißschuh
2025-09-03 11:21 ` (subset) " Catalin Marinas
2025-09-08 15:55 ` 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=175734490190.158300.1463560749148120421.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=jstultz@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=vincenzo.frascino@arm.com \
/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®