public inbox for linux-arm-kernel@lists.infradead.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 -rc3
Date: Fri, 6 Mar 2026 22:49:04 +0000	[thread overview]
Message-ID: <aatZ4AQK7IRQEQo8@willie-the-truck> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc3. The main changes are a fix to
the way in which we manage the access flag setting for mappings using
the contiguous bit and a fix for a hang on the kexec/hibernation path.

There's the usual summary in the tag.

Cheers,

Will

--->8

The following changes since commit df6e4ab654dc482c1d45776257a62ac10e14086c:

  arm64: topology: Fix false warning in counters_read_on_cpu() for same-CPU reads (2026-02-26 18:27:15 +0000)

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 d87c828daa7ead9763416f75cc416496969cf1dc:

  selftest/arm64: Fix sve2p1_sigill() to hwcap test (2026-03-06 11:54:26 +0000)

----------------------------------------------------------------
arm64 fixes for -rc3

- Fix kexec/hibernation hang due to bogus read-only mappings.

- Fix sparse warnings in our cmpxchg() implementation.

- Prevent runtime-const being used in modules, just like x86.

- Fix broken elision of access flag modifications for contiguous entries
  on systems without support for hardware updates.

- Fix a broken SVE selftest that was testing the wrong instruction.

----------------------------------------------------------------
Catalin Marinas (2):
      arm64: Silence sparse warnings caused by the type casting in (cmp)xchg
      arm64: mm: Add PTE_DIRTY back to PAGE_KERNEL* to fix kexec/hibernation

Jisheng Zhang (1):
      arm64: make runtime const not usable by modules

Piotr Jaroszynski (1):
      arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS faults

Yifan Wu (1):
      selftest/arm64: Fix sve2p1_sigill() to hwcap test

 arch/arm64/include/asm/cmpxchg.h          | 12 ++++---
 arch/arm64/include/asm/pgtable-prot.h     | 10 +++---
 arch/arm64/include/asm/runtime-const.h    |  4 +++
 arch/arm64/mm/contpte.c                   | 53 ++++++++++++++++++++++++++++---
 tools/testing/selftests/arm64/abi/hwcap.c |  4 +--
 5 files changed, 67 insertions(+), 16 deletions(-)


             reply	other threads:[~2026-03-06 22:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 22:49 Will Deacon [this message]
2026-03-07  4:34 ` [GIT PULL] arm64 fixes for -rc3 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-06-20 10:50 Will Deacon
2025-06-20 17:29 ` pr-tracker-bot
2025-02-14 14:04 Will Deacon
2025-02-14 19:29 ` pr-tracker-bot
2024-06-07 11:30 Will Deacon
2024-06-07 22:07 ` pr-tracker-bot
2024-02-02 11:11 Will Deacon
2024-02-02 20:43 ` pr-tracker-bot
2023-09-22 16:19 Will Deacon
2023-09-22 20:19 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22  0:07 ` Linus Torvalds
2020-02-22  0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31  4:25 ` pr-tracker-bot
2019-01-20  0:04 Will Deacon
2019-01-20  3:29 ` Linus Torvalds
2019-01-20  4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 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=aatZ4AQK7IRQEQo8@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