linux-kernel - Re: [PATCH v2] arm64/signal: Don't assume that TIF

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]

Date: Fri,  9 Feb 2024 18:31:06 +0000
From: Will Deacon <will@...nel.org>
To: Mark Brown <broonie@...nel.org>,
	Catalin Marinas <catalin.marinas@....com>
Cc: kernel-team@...roid.com,
	Will Deacon <will@...nel.org>,
	stable@...r.kernel.org,
	Dave Martin <Dave.Martin@....com>,
	linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] arm64/signal: Don't assume that TIF_SVE means we saved SVE state

On Tue, 30 Jan 2024 15:43:53 +0000, Mark Brown wrote:
> When we are in a syscall we will only save the FPSIMD subset even though
> the task still has access to the full register set, and on context switch
> we will only remove TIF_SVE when loading the register state. This means
> that the signal handling code should not assume that TIF_SVE means that
> the register state is stored in SVE format, it should instead check the
> format that was recorded during save.
> 
> [...]

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

[1/1] arm64/signal: Don't assume that TIF_SVE means we saved SVE state
      https://git.kernel.org/arm64/c/61da7c8e2a60

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev