From: Kees Cook <keescook@chromium.org>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: joseph@codesourcery.com, rguenther@suse.de, siddhesh@gotplt.org,
gcc-patches@gcc.gnu.org
Subject: Re: [V4][PATCH 0/2] Handle component_ref to a structure/union field including FAM for builtin_object_size
Date: Wed, 8 Mar 2023 10:45:36 -0800 [thread overview]
Message-ID: <6408d7d1.a70a0220.484be.1a2c@mx.google.com> (raw)
In-Reply-To: <20230224183505.4112295-1-qing.zhao@oracle.com>
On Fri, Feb 24, 2023 at 06:35:03PM +0000, Qing Zhao wrote:
> Hi, Joseph and Richard,
>
> Could you please review this patch and let me know whether it’s ready
> for committing into GCC13?
>
> The fix to Bug PR101832 is an important patch for kernel security
> purpose. it's better to be put into GCC13.
Hi!
This series tests well for me. Getting this landed would be very nice
for the Linux kernel. :)
Are there any additional review notes for it, or is it ready to land?
Thanks!
-Kees
--
Kees Cook
prev parent reply other threads:[~2023-03-08 18:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 18:35 Qing Zhao
2023-02-24 18:35 ` [v4][PATCH 1/2] Handle component_ref to a structre/union field including C99 FAM [PR101832] Qing Zhao
2023-03-03 0:03 ` Qing Zhao
2023-03-09 12:20 ` Richard Biener
2023-03-09 16:11 ` Qing Zhao
2023-03-10 7:54 ` Richard Biener
2023-03-10 13:48 ` Qing Zhao
2023-03-13 22:42 ` Qing Zhao
2023-03-14 9:04 ` Richard Biener
2023-03-14 13:09 ` Qing Zhao
2023-02-24 18:35 ` [V4][PATCH 2/2] Update documentation to clarify a GCC extension Qing Zhao
2023-03-03 0:03 ` Qing Zhao
2023-03-12 23:14 ` Sandra Loosemore
2023-03-13 12:46 ` Qing Zhao
2023-03-15 3:26 ` Sandra Loosemore
2023-03-15 14:42 ` Qing Zhao
2023-03-03 0:02 ` [V4][PATCH 0/2] Handle component_ref to a structure/union field including FAM for builtin_object_size Qing Zhao
2023-03-08 18:45 ` 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=6408d7d1.a70a0220.484be.1a2c@mx.google.com \
--to=keescook@chromium.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=qing.zhao@oracle.com \
--cc=rguenther@suse.de \
--cc=siddhesh@gotplt.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 read-only IMAP folder(s) and NNTP newsgroup(s).