Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Kees Cook <keescook@chromium.org>
To:     tglx@linutronix.de, keescook@chromium.org
Cc:     masahiroy@kernel.org, mingo@redhat.com, joanbrugueram@gmail.com,
        peterz@infradead.org, hi@alyssa.is, glider@google.com,
        dave.hansen@linux.intel.com, linux-kernel@vger.kernel.org,
        linux-hardening@vger.kernel.org, linux@leemhuis.info,
        samitolvanen@google.com, hpa@zytor.com, ndesaulniers@google.com,
        bp@alien8.de, gustavoars@kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86/purgatory: Do not use fortified string functions
Date:   Thu,  1 Jun 2023 09:57:49 -0700
Message-Id: <168563866754.2890079.16297092272263772482.b4-ty@chromium.org>
In-Reply-To: <20230531003345.never.325-kees@kernel.org>
References: <20230531003345.never.325-kees@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

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