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 [thread overview]
Message-ID: <168563866754.2890079.16297092272263772482.b4-ty@chromium.org> (raw)
In-Reply-To: <20230531003345.never.325-kees@kernel.org>
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
prev parent reply other threads:[~2023-06-01 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 0:33 [PATCH] x86/purgatory: Do not use fortified string functions Kees Cook
2023-05-31 7:51 ` Thorsten Leemhuis
2023-06-01 16:45 ` Dave Hansen
2023-06-01 16:50 ` Kees Cook
2023-06-01 16:57 ` 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=168563866754.2890079.16297092272263772482.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=glider@google.com \
--cc=gustavoars@kernel.org \
--cc=hi@alyssa.is \
--cc=hpa@zytor.com \
--cc=joanbrugueram@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).