From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Karl Mehltretter <kmehltretter@gmail.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>, Oleg Nesterov <oleg@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64/fpsimd: ptrace: Fix inactive SVE and SSVE regsets
Date: Sun, 2 Aug 2026 13:12:24 +0100 [thread overview]
Message-ID: <178566413306.4141663.7146790540592743319.b4-ty@kernel.org> (raw)
In-Reply-To: <20260729004255.15630-1-kmehltretter@gmail.com>
On Wed, 29 Jul 2026 02:42:54 +0200, Karl Mehltretter wrote:
> sve_init_header_from_task() takes header as a pointer, so for the
> inactive mode
>
> header->size = sizeof(header);
>
> stores 8 rather than sizeof(struct user_sve_header), which is 16.
> Userspace sees an impossible size smaller than the header it
> describes.
>
> [...]
Applied selftest update to arm64 (for-next/selftests), thanks!
[2/2] kselftest/arm64: fp-ptrace: Fix checks for inactive SVE and SSVE regsets
https://git.kernel.org/arm64/c/bd290e7fc245
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2026-08-02 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 0:42 [PATCH 1/2] arm64/fpsimd: ptrace: Fix inactive SVE and SSVE regsets Karl Mehltretter
2026-07-29 0:42 ` [PATCH 2/2] kselftest/arm64: fp-ptrace: Fix checks for " Karl Mehltretter
2026-08-02 12:12 ` Will Deacon [this message]
2026-08-05 21:27 ` [PATCH 1/2] arm64/fpsimd: ptrace: Fix " Mark Brown
2026-08-06 10:57 ` Will Deacon
2026-08-06 12:15 ` Mark Brown
2026-08-06 12:20 ` Will Deacon
2026-08-02 12:12 ` Will Deacon
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=178566413306.4141663.7146790540592743319.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=kmehltretter@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oleg@redhat.com \
--cc=shuah@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