mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 7.4-rc3
Date: Fri, 13 Nov 2026 18:52:41 +0000	[thread overview]
Message-ID: <20261113185244.3798402-1-catalin.marinas@arm.com> (raw)

Hi Linus,

Please pull the arm64 fixes below: hugetlb write fault livelock,
permission overlay and GCS state preservation across CPU suspend,
cpuidle context tracking during system suspend, GCS mode handling on
signal return, AMU counter errata workarounds, kexec loading of images
with a non-zero text_offset and a spurious ptrace warning.

Thanks.

The following changes since commit 58c1eb84e97701c583605ba2fd553b69afba2245:

  arm64: sdei: Preserve the interrupted context's exception registers (2026-11-06 17:43:20 +0000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes

for you to fetch changes up to ad3fc05c7e65009355effeea06aa629a687acef2:

  arm64: suspend: Only track cpuidle context for idle tasks (2026-11-13 17:12:34 +0000)

----------------------------------------------------------------
arm64 fixes:

 - Fix hugetlb write fault livelocks caused by stale read-only TLB
   entries after another CPU makes the page writable and only performs a
   local invalidate. Unlike the generic fault path, hugetlb has no
   fix_spurious_fault() fallback

 - Save and restore POR_EL0, GCSPR_EL0 and GCSCRE0_EL1 across CPU
   suspend

 - Restrict cpuidle context tracking in cpu_suspend() to idle tasks,
   avoiding context tracking warnings during system suspend

 - Ignore attempts to change GCS mode through signal return, which
   updated the software state without updating the hardware. Changes
   made through prctl() in the signal handler are preserved. This
   changes the documented ABI but no known userspace relies on it.
   Allowing mode changes through both prctl() and signal return also
   creates confusing interactions, with signal return potentially
   undoing changes deliberately made by the handler

 - Extend the AMU constant counter workaround to additional CPUs and
   add a core cycle counter workaround for Cortex-A715/A720, treating
   the affected counters as unavailable

 - Avoid CMA allocations when loading a kexec Image with a non-zero
   text_offset, fixing an incorrect entry point and a memory leak
   when freeing the image

 - Remove a spurious ptrace warning when setting the syscall number
   of a task in a non-seized group-stop without siginfo

----------------------------------------------------------------
Beata Michalska (2):
      arm64: errata: Extend the workaround for broken AMEVCNTR01 counter
      arm64: errata: Add Cortex-A715/A720 AMU core counter workaround

Chris Down (1):
      arm64: hugetlb: Prevent write fault livelocks on stale TLB entries

Jinjie Ruan (1):
      arm64: kexec_file: Do not use CMA for images with a non-zero text_offset

Mark Brown (3):
      arm64: suspend: Save POR_EL0 over suspend
      arm64: suspend: Save GCS state over suspend
      arm64/gcs: Ignore attempts to change GCS mode during signal return

Uladzislau Zhauniarovich (1):
      arm64: suspend: Only track cpuidle context for idle tasks

Zhao Gongyi (1):
      arm64: ptrace: don't warn on missing siginfo in a group-stop

 Documentation/arch/arm64/gcs.rst            | 13 +++------
 Documentation/arch/arm64/silicon-errata.rst | 12 ++++++++
 arch/arm64/Kconfig                          | 44 +++++++++++++++++++++++++++--
 arch/arm64/include/asm/suspend.h            |  2 +-
 arch/arm64/kernel/cpu_errata.c              | 28 ++++++++++++++++++
 arch/arm64/kernel/cpufeature.c              |  3 +-
 arch/arm64/kernel/kexec_image.c             |  7 +++++
 arch/arm64/kernel/ptrace.c                  |  8 ++++--
 arch/arm64/kernel/signal.c                  | 22 +--------------
 arch/arm64/kernel/suspend.c                 | 11 ++++++--
 arch/arm64/kernel/topology.c                |  3 +-
 arch/arm64/mm/hugetlbpage.c                 | 21 ++++++++++++--
 arch/arm64/mm/proc.S                        | 20 +++++++++++++
 arch/arm64/tools/cpucaps                    |  1 +
 14 files changed, 151 insertions(+), 44 deletions(-)

             reply	other threads:[~2026-11-13 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 18:52 Catalin Marinas [this message]
2026-11-13 22:03 ` pr-tracker-bot

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=20261113185244.3798402-1-catalin.marinas@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®