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 fix for 6.5-rc1
Date: Sat, 1 Jul 2023 17:15:08 +0100 [thread overview]
Message-ID: <ZKBRDMx96q25piLr@arm.com> (raw)
Hi Linus,
Here's an unplanned second pull request for -rc1 with a fix from Will
for the SVE registers saving corrupting memory. I'll be on holiday from
tomorrow for three weeks, checking the lists occasionally. If there's
anything urgent, Will should be around. Thanks.
The following changes since commit abc17128c81ae8d6a091f24348c63cbe8fe59724:
Merge branch 'for-next/feat_s1pie' into for-next/core (2023-06-23 18:34:16 +0100)
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 893b24181b4c4bf1fa2841b1ed192e5413a97cb1:
arm64: sme: Use STR P to clear FFR context field in streaming SVE mode (2023-06-29 11:29:31 +0100)
----------------------------------------------------------------
Fix memory corruption (overwriting the kmalloc redzone) when saving the
SVE state while in SVE streaming mode.
----------------------------------------------------------------
Will Deacon (1):
arm64: sme: Use STR P to clear FFR context field in streaming SVE mode
arch/arm64/include/asm/fpsimdmacros.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-07-01 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 16:15 Catalin Marinas [this message]
2023-07-01 16:17 ` [GIT PULL] arm64 fix for 6.5-rc1 Linus Torvalds
2023-07-01 16:19 ` 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=ZKBRDMx96q25piLr@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