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:     keescook@chromium.org, hca@linux.ibm.com
Cc:     svens@linux.ibm.com, gustavoars@kernel.org, agordeev@linux.ibm.com,
        linux@leemhuis.info, gor@linux.ibm.com, borntraeger@linux.ibm.com,
        linux-s390@vger.kernel.org, nathan@kernel.org,
        linux-hardening@vger.kernel.org, masahiroy@kernel.org,
        lkft@linaro.org, joanbrugueram@gmail.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/purgatory: Do not use fortified string functions
Date:   Thu,  1 Jun 2023 09:58:11 -0700
Message-Id: <168563869054.2890249.18018278036948799346.b4-ty@chromium.org>
In-Reply-To: <20230531003414.never.050-kees@kernel.org>
References: <20230531003414.never.050-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:34:15 -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] s390/purgatory: Do not use fortified string functions
      https://git.kernel.org/kees/c/d11f44513655

-- 
Kees Cook