From: Kees Cook <kees@kernel.org>
To: Martin Uecker <uecker@tugraz.at>
Cc: Joseph Myers <josmyers@redhat.com>,
Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] c: handle .ACCESS_WITH_SIZE in build_unary_op for !/+/- [PR125604]
Date: Fri, 19 Jun 2026 20:18:01 -0700 [thread overview]
Message-ID: <202606192017.EEACA7B@keescook> (raw)
In-Reply-To: <c4217b162310997b0a64603219543cc00ffa2227.camel@tugraz.at>
On Fri, Jun 19, 2026 at 11:36:10PM +0200, Martin Uecker wrote:
> Am Donnerstag, dem 18.06.2026 um 13:29 -0700 schrieb Kees Cook:
> > On Thu, Jun 18, 2026 at 12:56:51PM -0700, Kees Cook wrote:
> > > Unwrap the .ACCESS_WITH_SIZE call at the top of build_unary_op via
> > > get_ref_from_access_with_size. These unary operators consume the
> > > pointer rvalue rather than the pointed-to data, so the bounds-checking
> > > wrapper is not load-bearing here. The assertion is retained: after
> > > the unwrap it documents the post-condition the rest of the function
> > > relies on.
> >
> > BTW, I don't have commit access, so if this patch looks good, I still
> > need someone to commit for me. :)
>
> I committed it.
Yay! Thank you. :)
--
Kees Cook
prev parent reply other threads:[~2026-06-20 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 19:56 [PATCH v2] c: handle .ACCESS_WITH_SIZE in build_unary_op for !/+/- [PR125604] Kees Cook
2026-06-18 20:29 ` Kees Cook
2026-06-19 21:36 ` Martin Uecker
2026-06-20 3:18 ` 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=202606192017.EEACA7B@keescook \
--to=kees@kernel.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=josmyers@redhat.com \
--cc=linux-hardening@vger.kernel.org \
--cc=rguenther@suse.de \
--cc=uecker@tugraz.at \
/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.