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,
	maz@kernel.org, mark.rutland@arm.com
Subject: [GIT PULL] arm64 fixes for 6.16
Date: Thu, 24 Jul 2025 10:44:06 +0100	[thread overview]
Message-ID: <aIIAZiQ6ca3DFHpE@willie-the-truck> (raw)

Hi Linus,

Please pull these two important arm64 fixes ahead of the 6.16 release.

The first fixes a regression introduced during the merge window where
the KVM UUID (which is used to advertise KVM-specific hypercalls for
things like time synchronisation in the guest) was corrupted thanks to
an endianness bug introduced when converting the code to use the
UUID_INIT() helper.

The second fixes a stack-pointer corruption issue during context-switch
which has been observed in the wild when taking a pseudo-NMI with
shadow call stack enabled.

Please pull.

Cheers,

Will

--->8

The following changes since commit 9dd1757493416310a5e71146a08bc228869f8dae:

  arm64/mm: Drop wrong writes into TCR2_EL1 (2025-07-04 16:46:04 +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 d42e6c20de6192f8e4ab4cf10be8c694ef27e8cb:

  arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() (2025-07-22 16:39:30 +0100)

----------------------------------------------------------------
arm64 fixes for 6.16

- Fix broken UUID value for the KVM/arm64 hypervisor SMCCC interface.

- Fix stack corruption on context-switch, primarily seen on (but not
  limited to) configurations with both pNMI and SCS enabled.

----------------------------------------------------------------
Ada Couprie Diaz (1):
      arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack()

Jack Thomson (1):
      arm64: kvm, smccc: Fix vendor uuid

 arch/arm64/include/asm/assembler.h | 5 +++++
 arch/arm64/kernel/entry.S          | 6 ++++++
 include/linux/arm-smccc.h          | 2 +-
 3 files changed, 12 insertions(+), 1 deletion(-)


             reply	other threads:[~2025-07-24 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24  9:44 Will Deacon [this message]
2025-07-24 16:56 ` [GIT PULL] arm64 fixes for 6.16 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=aIIAZiQ6ca3DFHpE@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=mark.rutland@arm.com \
    --cc=maz@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