linux-kernel - Re: [PATCH] arm64/ptrace: Clarify documentation of VL configuration via ptrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <173142780465.896456.9873316347312765271.b4-ty@arm.com>
Date: Tue, 12 Nov 2024 16:10:19 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Will Deacon <will@...nel.org>,
	Jonathan Corbet <corbet@....net>,
	Oleg Nesterov <oleg@...hat.com>,
	Mark Brown <broonie@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org,
	linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64/ptrace: Clarify documentation of VL configuration via ptrace

On Wed, 06 Nov 2024 17:41:32 +0000, Mark Brown wrote:
> When we configure SVE, SSVE or ZA via ptrace we allow the user to configure
> the vector length and specify any of the flags that are accepted when
> configuring via prctl(). This includes the S[VM]E_SET_VL_ONEXEC flag which
> defers the configuration of the VL until an exec(). We don't do anything to
> limit the provision of register data as part of configuring the _ONEXEC VL
> but as a function of the VL enumeration support we do this will be
> interpreted using the vector length currently configured for the process.
> 
> [...]

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64/ptrace: Clarify documentation of VL configuration via ptrace
      https://git.kernel.org/arm64/c/c0139f6cbb1f

-- 
Catalin