From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
broonie@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems
Date: Thu, 1 Oct 2026 16:50:43 +0100 [thread overview]
Message-ID: <179086063838.2740899.986966739708665243.b4-ty@kernel.org> (raw)
In-Reply-To: <20261001130836.1410888-1-mark.rutland@arm.com>
On Thu, 01 Oct 2026 14:08:36 +0100, Mark Rutland wrote:
> When system_supports_sme() is true but system_supports_sve() is false,
> restoring a specifically crafted SVE signal context can result in the
> task erroneously having non-streaming SVE state. Subsequent attempts to
> manipulate the task's FPSIMD/SVE/SME state can result in a variety of
> problems, including fatal EL1 UNDEFs.
>
> In such configurations, the kernel always creates an SVE signal context
> when delivering a signal, and this can only be in one of two states:
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems
https://git.kernel.org/arm64/c/e060d9069b49
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-10-01 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:08 [PATCH] arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems Mark Rutland
2026-10-01 14:25 ` Mark Brown
2026-10-01 14:42 ` Mark Rutland
2026-10-01 15:50 ` Will Deacon [this message]
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=179086063838.2740899.986966739708665243.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=stable@vger.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