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.19-rc7
Date: Fri, 23 Jan 2026 18:37:30 +0000 [thread overview]
Message-ID: <aXO_6oqyqGevo4XW@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit b9f5c38e4af1a094384650d2fc79fb992d6d5e64:
arm_mpam: Use non-atomic bitops when modifying feature bitmap (2026-01-16 12:04: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 e2f8216ca2d8e61a23cb6ec355616339667e0ba6:
arm64: Set __nocfi on swsusp_arch_resume() (2026-01-23 18:13:07 +0000)
----------------------------------------------------------------
arm64 fixes:
- A set of fixes for FPSIMD/SVE/SME state management (around signal
handling and ptrace) where a task can be placed in an invalid state
- __nocfi added to swsusp_arch_resume() to avoid a data abort on
resuming from hibernate
----------------------------------------------------------------
Mark Rutland (3):
arm64/fpsimd: ptrace: Fix SVE writes on !SME systems
arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA
arm64/fpsimd: signal: Fix restoration of SVE context
Zhaoyang Huang (1):
arm64: Set __nocfi on swsusp_arch_resume()
arch/arm64/kernel/hibernate.c | 2 +-
arch/arm64/kernel/ptrace.c | 26 ++++++++++++--------------
arch/arm64/kernel/signal.c | 26 ++++++++++++++++++++------
3 files changed, 33 insertions(+), 21 deletions(-)
--
Catalin
next reply other threads:[~2026-01-23 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 18:37 Catalin Marinas [this message]
2026-01-23 22:03 ` [GIT PULL] arm64 fixes for 6.19-rc7 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=aXO_6oqyqGevo4XW@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox