From: Kees Cook <kees@kernel.org>
To: Joseph Myers <josmyers@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
Martin Uecker <uecker@tugraz.at>,
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: Thu, 18 Jun 2026 13:29:24 -0700 [thread overview]
Message-ID: <202606181328.ABB25F969C@keescook> (raw)
In-Reply-To: <20260618195646.it.067-kees@kernel.org>
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. :)
--
Kees Cook
next prev parent reply other threads:[~2026-06-18 20:29 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 [this message]
2026-06-19 21:36 ` Martin Uecker
2026-06-20 3:18 ` Kees Cook
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=202606181328.ABB25F969C@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox