[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164668908127.3275060.4752923202018767533.b4-ty@kernel.org>
Date: Mon, 7 Mar 2022 22:03:29 +0000
From: Will Deacon <will@...nel.org>
To: ebiederm@...ssion.com, suzuki.poulose@....com,
mark.rutland@....com, elver@...gle.com, seanjc@...gle.com,
broonie@...nel.org, David Engraf <david.engraf@...go.com>,
catalin.marinas@....com
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: signal: nofpsimd: Do not allocate fp/simd context when not available
On Fri, 25 Feb 2022 11:40:08 +0100, David Engraf wrote:
> Commit 6d502b6ba1b2 ("arm64: signal: nofpsimd: Handle fp/simd context for
> signal frames") introduced saving the fp/simd context for signal handling
> only when support is available. But setup_sigframe_layout() always
> reserves memory for fp/simd context. The additional memory is not touched
> because preserve_fpsimd_context() is not called and thus the magic is
> invalid.
>
> [...]
Applied to arm64 (for-next/fpsimd), thanks!
[1/1] arm64: signal: nofpsimd: Do not allocate fp/simd context when not available
https://git.kernel.org/arm64/c/0a32c88ddb9a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists