[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <163888363674.3690807.16904122616287532498.b4-ty@ellerman.id.au>
Date: Wed, 08 Dec 2021 00:27:16 +1100
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Michael Ellerman <mpe@...erman.id.au>,
Kees Cook <keescook@...omium.org>
Cc: Nicholas Piggin <npiggin@...il.com>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
linux-hardening@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Sudeep Holla <sudeep.holla@....com>,
Paul Mackerras <paulus@...ba.org>,
kernel test robot <lkp@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linuxppc-dev@...ts.ozlabs.org,
Christophe Leroy <christophe.leroy@...roup.eu>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] powerpc/signal32: Use struct_group() to zero spe regs
On Thu, 18 Nov 2021 12:36:04 -0800, Kees Cook wrote:
> In preparation for FORTIFY_SOURCE performing compile-time and run-time
> field bounds checking for memset(), avoid intentionally writing across
> neighboring fields.
>
> Add a struct_group() for the spe registers so that memset() can correctly reason
> about the size:
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/signal32: Use struct_group() to zero spe regs
https://git.kernel.org/powerpc/c/62ea67e31981bca95ec16c37e2a1fba68f3dd8c5
cheers
Powered by blists - more mailing lists