From: Kees Cook <keescook@chromium.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] gcc-plugins: randstruct: Update code comment in relayout_struct()
Date: Mon, 27 Nov 2023 16:34:36 -0800 [thread overview]
Message-ID: <170113167459.1670911.15084763564199264156.b4-ty@chromium.org> (raw)
In-Reply-To: <ZWJr2MWDjXLHE8ap@work>
On Sat, 25 Nov 2023 15:49:12 -0600, Gustavo A. R. Silva wrote:
> Update code comment to clarify that the only element whose layout is
> not randomized is a proper C99 flexible-array member. This update is
> complementary to commit 1ee60356c2dc ("gcc-plugins: randstruct: Only
> warn about true flexible arrays")
>
>
Applied to for-linus/hardening, thanks!
[1/1] gcc-plugins: randstruct: Update code comment in relayout_struct()
https://git.kernel.org/kees/c/d71f22365a9c
Take care,
--
Kees Cook
prev parent reply other threads:[~2023-11-28 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 21:49 [PATCH][next] gcc-plugins: randstruct: Update code comment in relayout_struct() Gustavo A. R. Silva
2023-11-28 0:34 ` 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=170113167459.1670911.15084763564199264156.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.