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;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] riscv/purgatory: Do not use fortified string functions
From:   patchwork-bot+linux-riscv@kernel.org
Message-Id: <168565081984.8603.17593394447980152382.git-patchwork-notify@kernel.org>
Date:   Thu, 01 Jun 2023 20:20:19 +0000
References: <20230601160025.gonna.868-kees@kernel.org>
In-Reply-To: <20230601160025.gonna.868-kees@kernel.org>
To:     Kees Cook <keescook@chromium.org>
Cc:     linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
        linux@leemhuis.info, joanbrugueram@gmail.com, palmer@dabbelt.com,
        aou@eecs.berkeley.edu, masahiroy@kernel.org,
        conor.dooley@microchip.com, ndesaulniers@google.com, hi@alyssa.is,
        heiko.stuebner@vrull.eu, gustavoars@kernel.org,
        ajones@ventanamicro.com, linux-kernel@vger.kernel.org,
        linux-hardening@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Thu,  1 Jun 2023 09:00:28 -0700 you 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];
> };
> 
> [...]

Here is the summary with links:
  - [v2] riscv/purgatory: Do not use fortified string functions
    https://git.kernel.org/riscv/c/0f84097ab015

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html