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 [thread overview]
Message-ID: <168563869054.2890249.18018278036948799346.b4-ty@chromium.org> (raw)
In-Reply-To: <20230531003414.never.050-kees@kernel.org>
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
prev parent reply other threads:[~2023-06-01 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 0:34 [PATCH] s390/purgatory: Do not use fortified string functions Kees Cook
2023-05-31 14:33 ` Nathan Chancellor
2023-06-01 16:58 ` Kees Cook [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=168563869054.2890249.18018278036948799346.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=gustavoars@kernel.org \
--cc=hca@linux.ibm.com \
--cc=joanbrugueram@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lkft@linaro.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=svens@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).