From: Mark Brown <broonie@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, Will Deacon <will@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
live-patching@vger.kernel.org, Song Liu <song@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Mark Rutland <mark.rutland@arm.com>, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] arm64/module: Fix livepatch BTI exceptions with Clang 21+
Date: Tue, 11 Aug 2026 18:23:03 +0100 [thread overview]
Message-ID: <ad261bfa-5301-4b3c-a146-86111d15e644@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOdkVxt-90Z_Af8s63RKCY-202r_0_bgF+8-g7iKn6XM_Sg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Tue, Aug 11, 2026 at 09:17:09AM -0700, Nick Desaulniers wrote:
> On Tue, Aug 11, 2026 at 6:18 AM Ard Biesheuvel <ardb@kernel.org> wrote:
> > https://github.com/llvm/llvm-project/issues/215547
> Thanks.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106671 was closed as
> invalid pointing to the same commit in llvm. What's going on here?
> Where's the corresponding feature request for GCC?
TBH I'd missed that that got closed, basically it's what's in the report
there - the GCC people really dislike the idea of adding landing pads
and want to see veneers added by the linker to fix up issues where
they're missing.
> At the least, I could imagine there being a `-fno-omit-bti-pads` or
> whatever for the kernel to opt into this behavior.
That would be useful.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-08-11 17:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 21:46 [PATCH] arm64/module: Fix livepatch BTI exceptions with Clang 21+ Josh Poimboeuf
2026-08-07 22:00 ` sashiko-bot
2026-08-10 10:31 ` Will Deacon
2026-08-10 15:48 ` Josh Poimboeuf
2026-08-10 16:12 ` Ard Biesheuvel
2026-08-10 16:39 ` Josh Poimboeuf
2026-08-10 16:41 ` Nick Desaulniers
2026-08-11 9:44 ` Will Deacon
2026-08-11 12:02 ` Ard Biesheuvel
2026-08-11 13:18 ` Ard Biesheuvel
2026-08-11 14:23 ` Will Deacon
2026-08-11 14:55 ` Ard Biesheuvel
2026-08-11 15:05 ` Josh Poimboeuf
2026-08-11 16:27 ` Nick Desaulniers
2026-08-11 16:41 ` Josh Poimboeuf
2026-08-11 16:52 ` Nick Desaulniers
2026-08-11 16:54 ` Ard Biesheuvel
2026-08-11 17:05 ` Nick Desaulniers
2026-08-11 17:08 ` Ard Biesheuvel
2026-08-11 16:17 ` Nick Desaulniers
2026-08-11 17:23 ` Mark Brown [this message]
2026-08-10 16:25 ` Mark Brown
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=ad261bfa-5301-4b3c-a146-86111d15e644@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=ndesaulniers@google.com \
--cc=pmladek@suse.com \
--cc=song@kernel.org \
--cc=will@kernel.org \
/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