[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168563866754.2890079.16297092272263772482.b4-ty@chromium.org>
Date: Thu, 1 Jun 2023 09:57:49 -0700
From: Kees Cook <keescook@...omium.org>
To: tglx@...utronix.de, keescook@...omium.org
Cc: masahiroy@...nel.org, mingo@...hat.com, joanbrugueram@...il.com,
peterz@...radead.org, hi@...ssa.is, glider@...gle.com,
dave.hansen@...ux.intel.com, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org, linux@...mhuis.info,
samitolvanen@...gle.com, hpa@...or.com, ndesaulniers@...gle.com,
bp@...en8.de, gustavoars@...nel.org, x86@...nel.org
Subject: Re: [PATCH] x86/purgatory: Do not use fortified string functions
On Tue, 30 May 2023 17:33:48 -0700, Kees Cook wrote:
> With the addition of -fstrict-flex-arrays=3, struct sha256_state's
> trailing array is no longer ignored by CONFIG_FORTIFY_SOURCE:
>
> struct sha256_state {
> u32 state[SHA256_DIGEST_SIZE / 4];
> u64 count;
> u8 buf[SHA256_BLOCK_SIZE];
> };
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] x86/purgatory: Do not use fortified string functions
https://git.kernel.org/kees/c/f6ab7fc96a53
--
Kees Cook
Powered by blists - more mailing lists