From: Ard Biesheuvel <ardb+git@google.com>
To: linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, will@kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
Mark Brown <broonie@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [PATCH 0/3] arm64: Combine module .init.text with .text
Date: Thu, 19 Nov 2026 17:58:26 +0100 [thread overview]
Message-ID: <20261119165825.1793558-5-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
This is a follow-up to "arm64: Implement support for BTI veneers" [0]
which adds support to the module loader for indirect calls to functions
that were emitted by the compiler without a BTI landing pad.
This series takes the ppc approach, and simply combines .init.text with
.text when loading modules, so that cross-section calls in the same
module (which may originate in the same compilation unit) can never go
out of direct branching range.
This makes the BTI veneer solution unnecessary, and permits some other
simplifications that were added, even though .init.text and .text rarely
end up far away from each other in practice.
Live patch needs additional work, so BTI remains disabled when live patch
is enabled. (It expects to be able to make indirect calls to any
function in vmlinux or elsewhere, even if they were never exported)
Cc: Mark Brown <broonie@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>
[0] https://lore.kernel.org/all/20261005110511.157016-4-ardb+git@google.com/
Ard Biesheuvel (3):
arm64: module: Keep executable init sections in the core text region
arm64: Re-enable kernel BTI for compatible linkers
arm64: module: Revert separate init PLT and init ftrace trampoline
arch/arm64/Kconfig | 17 ++--
arch/arm64/include/asm/module.h | 11 +--
arch/arm64/include/asm/module.lds.h | 2 -
arch/arm64/kernel/ftrace.c | 13 +--
arch/arm64/kernel/module-plts.c | 98 +++++++-------------
arch/arm64/kernel/module.c | 46 ++++++---
6 files changed, 84 insertions(+), 103 deletions(-)
--
2.56.1.708.g77570a6a1d-goog
next reply other threads:[~2026-11-19 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 16:58 Ard Biesheuvel [this message]
2026-11-19 16:58 ` [PATCH 1/3] arm64: module: Keep executable init sections in the core text region Ard Biesheuvel
2026-11-19 16:58 ` [PATCH 2/3] arm64: Re-enable kernel BTI for compatible linkers Ard Biesheuvel
2026-11-19 16:58 ` [PATCH 3/3] arm64: module: Revert separate init PLT and init ftrace trampoline Ard Biesheuvel
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=20261119165825.1793558-5-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jpoimboe@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ndesaulniers@google.com \
--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