From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Kees Cook <keescook@chromium.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: "Joel Stanley" <joel@jms.id.au>,
linux-i3c@lists.infradead.org,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Matt Johnston" <matt@codeconstruct.com.au>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Jack Chen" <zenghuchen@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] i3c: dw: Annotate struct dw_i3c_xfer with __counted_by
Date: Fri, 22 Sep 2023 11:48:11 -0700 [thread overview]
Message-ID: <66b317e630f6904cbddbb8affcf06b59b4c0ead8.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20230922175011.work.800-kees@kernel.org>
Hi Kees,
> Prepare for the coming implementation by GCC and Clang of the
> __counted_by attribute. Flexible array members annotated with
> __counted_by can have their accesses bounds-checked at run-time
> checking via CONFIG_UBSAN_BOUNDS (for array indexing) and
> CONFIG_FORTIFY_SOURCE (for strcpy/memcpy- family functions).
Nice!
Reviewed-by: Jeremy Kerr <jk@codeconstruct.com.au>
Cheers,
Jeremy
next prev parent reply other threads:[~2023-09-22 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 17:50 [PATCH] i3c: dw: Annotate struct dw_i3c_xfer with __counted_by Kees Cook
2023-09-22 18:48 ` Jeremy Kerr [this message]
2023-09-23 17:00 ` Gustavo A. R. Silva
2023-09-25 21:36 ` Alexandre Belloni
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=66b317e630f6904cbddbb8affcf06b59b4c0ead8.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=alexandre.belloni@bootlin.com \
--cc=joel@jms.id.au \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=matt@codeconstruct.com.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zenghuchen@google.com \
/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