Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 -rc1
Date: Thu, 5 Jun 2025 14:41:26 +0100	[thread overview]
Message-ID: <20250605134126.GA4845@willie-the-truck> (raw)

Hi Linus,

Please pull the following arm64 fixes for -rc1. Usual summary in the
tag, but we've got a couple of build fixes when using LLD, a missing TLB
invalidation and a workaround for broken firmware on SoCs with CPUs that
implement MPAM.

Cheers,

Will

--->8

The following changes since commit 217e3cbba3d6613bee9ac33ddc330f8676eb9eca:

  Merge branch 'for-next/vdso' into for-next/core (2025-05-27 12:26:54 +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 10f885d63a0efd50b0d22bf27eb3cf727838e99e:

  arm64: Add override for MPAM (2025-06-02 13:49:09 +0100)

----------------------------------------------------------------
arm64 fixes for -rc1

- Disable problematic linker assertions for broken versions of LLD.

- Work around sporadic link failure with LLD and various randconfig
  builds.

- Fix missing invalidation in the TLB batching code when reclaim races
  with mprotect() and friends.

- Add a command-line override for MPAM to allow booting on systems with
  broken firmware.

----------------------------------------------------------------
Ard Biesheuvel (2):
      arm64: Disable LLD linker ASSERT()s for the time being
      arm64: Work around convergence issue with LLD linker

Ryan Roberts (1):
      arm64/mm: Close theoretical race where stale TLB entry remains valid

Xi Ruoyao (1):
      arm64: Add override for MPAM

 Documentation/admin-guide/kernel-parameters.txt |  3 +++
 arch/arm64/include/asm/el2_setup.h              | 24 ++++++++++--------------
 arch/arm64/include/asm/kernel-pgtable.h         |  2 +-
 arch/arm64/include/asm/tlbflush.h               |  9 +++++----
 arch/arm64/kernel/cpufeature.c                  |  7 +++++--
 arch/arm64/kernel/cpuinfo.c                     |  7 +++++--
 arch/arm64/kernel/image-vars.h                  | 17 +++++++++++++++++
 arch/arm64/kernel/pi/idreg-override.c           |  3 +++
 8 files changed, 49 insertions(+), 23 deletions(-)


             reply	other threads:[~2025-06-05 14:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 13:41 Will Deacon [this message]
2025-06-05 18:53 ` [GIT PULL] arm64 fixes for -rc1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-06-26 10:59 Will Deacon
2026-06-26 15:45 ` pr-tracker-bot
2026-02-20 15:41 Will Deacon
2026-02-20 20:50 ` pr-tracker-bot
2025-10-07  8:28 Will Deacon
2025-10-07 16:13 ` pr-tracker-bot
2024-07-26  8:42 Will Deacon
2024-07-26 18:07 ` pr-tracker-bot
2024-05-23 10:20 Will Deacon
2024-05-23 19:28 ` pr-tracker-bot
2024-01-19 16:05 Will Deacon
2024-01-19 16:34 ` Rob Herring
2024-01-19 16:58   ` Rob Herring
2024-01-19 22:50 ` pr-tracker-bot
2023-09-08 15:30 Will Deacon
2023-09-08 20:00 ` pr-tracker-bot
2023-05-04 14:22 Will Deacon
2023-05-04 19:49 ` pr-tracker-bot
2022-12-16 15:51 Will Deacon
2022-12-16 19:50 ` pr-tracker-bot
2021-11-10 18:52 Will Deacon
2021-11-10 20:09 ` pr-tracker-bot
2021-02-26 11:09 [GIT PULL] arm64: Fixes " Will Deacon
2021-02-26 18:31 ` pr-tracker-bot
2019-09-20 13:37 Will Deacon
2019-09-20 19:10 ` pr-tracker-bot
2019-01-04 18:24 [GIT PULL] arm64: fixes " Will Deacon
2019-01-05 20:20 ` pr-tracker-bot
2017-03-01  4:51 [GIT PULL] arm64 " Will Deacon
2016-08-05 15:48 [GIT PULL] arm64: " Will Deacon
2014-12-16 17:50 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=20250605134126.GA4845@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