[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168565081984.8603.17593394447980152382.git-patchwork-notify@kernel.org>
Date: Thu, 01 Jun 2023 20:20:19 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Kees Cook <keescook@...omium.org>
Cc: linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com,
linux@...mhuis.info, joanbrugueram@...il.com, palmer@...belt.com,
aou@...s.berkeley.edu, masahiroy@...nel.org,
conor.dooley@...rochip.com, ndesaulniers@...gle.com, hi@...ssa.is,
heiko.stuebner@...ll.eu, gustavoars@...nel.org,
ajones@...tanamicro.com, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2] riscv/purgatory: Do not use fortified string functions
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@...osinc.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
Powered by blists - more mailing lists