From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc6
Date: Tue, 11 Nov 2025 18:07:58 +0000 [thread overview]
Message-ID: <aRN7fm_q2B5UzQTK@willie-the-truck> (raw)
Hi Linus,
Please pull these arm64 fixes for -rc6. There's more here than I would
ideally like at this stage, but there's been a steady trickle of fixes
and some of them took a few rounds of review.
The bulk of the changes are fixing some fallout from the recent BBM
level two support which allows the linear map to be split from block to
page mappings at runtime, but inadvertently led to sleeping in atomic
context on some paths where the linear map was already mapped with page
granularity. The fix is simply to avoid splitting in those cases but the
implementation of that is a little involved.
The other interesting fix is addressing a catastophic performance issue
with our per-cpu atomics discovered by Paul in the SRCU locking code but
which took some interactions with the hardware folks to resolve.
Anyway, summary in the tag. Please pull.
Cheers,
Will
--->8
The following changes since commit b98c94eed4a975e0c80b7e90a649a46967376f58:
arm64: mte: Do not warn if the page is already tagged in copy_highpage() (2025-10-23 17:34:58 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to 8e8ae788964aa2573b4335026db4068540fa6a86:
arm64: Reject modules with internal alternative callbacks (2025-11-07 15:00:14 +0000)
----------------------------------------------------------------
arm64 fixes for -rc6
- Avoid sleeping in atomic context when changing linear map permissions
for DEBUG_PAGEALLOC or KFENCE.
- Rework printing of Spectre mitigation status to avoid hardlockup when
enabling per-task mitigations on the context-switch path.
- Reject kernel modules when instruction patching fails either due to
the DWARF-based SCS patching or because of an alternatives callback
residing outside of the core kernel text.
- Propagate error when updating kernel memory permissions in kprobes.
- Drop pointless, incorrect message when enabling the ACPI SPCR console.
- Use value-returning LSE instructions for per-cpu atomics to reduce
latency in SRCU locking routines.
----------------------------------------------------------------
Adrian Barnaś (2):
arm64: Fail module loading if dynamic SCS patching fails
arm64: Reject modules with internal alternative callbacks
Catalin Marinas (1):
arm64: Use load LSE atomics for the non-return per-CPU atomic operations
Punit Agrawal (2):
Revert "ACPI: Suppress misleading SPCR console message when SPCR table is absent"
arm64: acpi: Drop message logging SPCR default console
Ryan Roberts (3):
arm64: mm: Don't sleep in split_kernel_leaf_mapping() when in atomic context
arm64: mm: Optimize range_split_to_ptes()
arm64: mm: Tidy up force_pte_mapping()
Yang Shi (1):
arm64: kprobes: check the return value of set_memory_rox()
shechenglong (2):
arm64: proton-pack: Drop print when !CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY
arm64: proton-pack: Fix hard lockup due to print in scheduler context
arch/arm64/include/asm/alternative.h | 7 ++-
arch/arm64/include/asm/kfence.h | 3 +-
arch/arm64/include/asm/percpu.h | 15 +++--
arch/arm64/include/asm/scs.h | 2 +-
arch/arm64/include/asm/spectre.h | 1 +
arch/arm64/kernel/acpi.c | 8 +--
arch/arm64/kernel/alternative.c | 19 +++---
arch/arm64/kernel/cpufeature.c | 6 ++
arch/arm64/kernel/module.c | 21 +++++--
arch/arm64/kernel/pi/map_kernel.c | 2 +-
arch/arm64/kernel/pi/patch-scs.c | 10 ++--
arch/arm64/kernel/pi/pi.h | 2 +-
arch/arm64/kernel/probes/kprobes.c | 5 +-
arch/arm64/kernel/proton-pack.c | 35 +++++------
arch/arm64/mm/mmu.c | 111 +++++++++++++++++++++++++----------
15 files changed, 165 insertions(+), 82 deletions(-)
next reply other threads:[~2025-11-11 18:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 18:07 Will Deacon [this message]
2025-11-11 19:10 ` [GIT PULL] arm64 fixes for -rc6 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-07-09 15:08 Will Deacon
2025-07-09 18:37 ` pr-tracker-bot
2024-11-01 11:22 Will Deacon
2024-11-01 18:34 ` pr-tracker-bot
2024-06-28 8:59 Will Deacon
2024-06-28 17:01 ` pr-tracker-bot
2024-02-23 10:25 Will Deacon
2024-02-23 18:44 ` pr-tracker-bot
2023-06-08 20:51 Will Deacon
2023-06-08 21:49 ` pr-tracker-bot
2021-12-15 11:19 Will Deacon
2021-12-15 16:00 ` Catalin Marinas
2021-12-15 18:49 ` Linus Torvalds
2020-11-27 11:40 Will Deacon
2020-11-27 19:19 ` pr-tracker-bot
2020-07-17 15:20 Will Deacon
2020-07-17 23:45 ` pr-tracker-bot
2019-11-01 14:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-11-01 17:10 ` pr-tracker-bot
2019-08-24 12:12 Will Deacon
2019-08-24 18:45 ` pr-tracker-bot
2019-06-20 16:59 [GIT PULL] arm64: fixes " Will Deacon
2019-06-20 19:10 ` pr-tracker-bot
2019-02-08 17:35 Will Deacon
2019-02-09 0:40 ` pr-tracker-bot
2017-04-07 16:02 Will Deacon
2017-04-11 19:12 ` Jon Masters
2017-04-12 9:14 ` Will Deacon
2017-04-12 10:18 ` Punit Agrawal
2015-10-15 13:38 Will Deacon
2015-01-23 16:44 Will Deacon
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=aRN7fm_q2B5UzQTK@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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