All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <cmarinas@kernel.org>
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 6.17-rc4
Date: Sat, 30 Aug 2025 13:55:52 +0100	[thread overview]
Message-ID: <aLL02Fi-gazNRa1G@arm.com> (raw)

Hi Linus,

Please pull a couple of small arm64 fixes below (for -rc4 if there's
still time, otherwise -rc5 is fine as well). Thanks.

The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

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

  kselftest/arm64: Don't open code SVE_PT_SIZE() in fp-ptrace (2025-08-30 11:31:11 +0100)

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

- CFI failure due to kpti_ng_pgd_alloc() signature mismatch

- Underallocation bug in the SVE ptrace kselftest

----------------------------------------------------------------
Kees Cook (1):
      arm64: mm: Fix CFI failure due to kpti_ng_pgd_alloc function signature

Mark Brown (1):
      kselftest/arm64: Don't open code SVE_PT_SIZE() in fp-ptrace

 arch/arm64/include/asm/mmu.h                 | 7 +++++++
 arch/arm64/kernel/cpufeature.c               | 5 +++--
 arch/arm64/mm/mmu.c                          | 7 -------
 tools/testing/selftests/arm64/fp/fp-ptrace.c | 5 ++---
 4 files changed, 12 insertions(+), 12 deletions(-)

-- 
Catalin


             reply	other threads:[~2025-08-30 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-30 12:55 Catalin Marinas [this message]
2025-08-30 17:56 ` [GIT PULL] arm64 fixes for 6.17-rc4 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=aLL02Fi-gazNRa1G@arm.com \
    --to=cmarinas@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.