public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Rosen Penev" <rosenp@gmail.com>
Cc: "Thorsten Blum" <thorsten.blum@linux.dev>,
	"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
	"Kees Cook" <kees@kernel.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-hardening@vger.kernel.org>,
	"Romain Gantois" <romain.gantois@bootlin.com>
Subject: Re: [PATCH] i2c: atr: annotate i2c_atr_adap_desc->aliases with __counted_by_ptr
Date: Wed, 29 Apr 2026 12:39:00 +0200	[thread overview]
Message-ID: <DI5KOGI4TE9X.20PGGVLRJCJHF@bootlin.com> (raw)
In-Reply-To: <CAKxU2N8OUcsTxG4XDH=cbROz4954-V5ximN-XHQ5RrPagTfUjQ@mail.gmail.com>

On Tue Apr 28, 2026 at 10:27 PM CEST, Rosen Penev wrote:
> On Tue, Apr 28, 2026 at 2:30 AM Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
>>
>> Hello Thorsten,
>>
>> +Cc Romain, author of the involved code
>> +Cc Rosen, author of a similar patch elsewhere in i2c-atr [0]
>>
>> [0] https://lore.kernel.org/linux-i2c/20260327030310.8502-1-rosenp@gmail.com/
>>
>> On Mon Apr 27, 2026 at 7:28 PM CEST, Thorsten Blum wrote:
>> > Add the __counted_by_ptr() compiler attribute to ->aliases to improve
>> > bounds checking via CONFIG_UBSAN_BOUNDS and CONFIG_FORTIFY_SOURCE.
>> >
>> > Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
>> > ---
>> >  include/linux/i2c-atr.h | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/include/linux/i2c-atr.h b/include/linux/i2c-atr.h
>> > index 2bb54dc87c8e..b52a7b9ec536 100644
>> > --- a/include/linux/i2c-atr.h
>> > +++ b/include/linux/i2c-atr.h
>> > @@ -71,7 +71,7 @@ struct i2c_atr_adap_desc {
>> >       struct device *parent;
>> >       struct fwnode_handle *bus_handle;
>> >       size_t num_aliases;
>> > -     u16 *aliases;
>> > +     u16 *aliases __counted_by_ptr(num_aliases);
>>
>> I'm not fully proficient about all counted_by things, but the patch looks
>> OK to me, and definitely @num_aliases is the number of items @aliases must
>> have, so:
> I prefer my patch.
>
> __counted_by is supported by more versions of GCC/Clang than __counted_by_ptr.

At a quick grep check, they seem to be different things: __counted_by for
arrays embedded in structs, __counted_by_ptr for pointers in structs for
dynamically allocated arrays. I wish this were documented, though,
especially as their implementation is currently identical. :-/

Based on this, I think both Rosen's and Thorsten's changes are OK, using
different macros for different members.

Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2026-04-29 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 17:28 [PATCH] i2c: atr: annotate i2c_atr_adap_desc->aliases with __counted_by_ptr Thorsten Blum
2026-04-28  9:29 ` Luca Ceresoli
2026-04-28 20:27   ` Rosen Penev
2026-04-29 10:39     ` Luca Ceresoli [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=DI5KOGI4TE9X.20PGGVLRJCJHF@bootlin.com \
    --to=luca.ceresoli@bootlin.com \
    --cc=gustavoars@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romain.gantois@bootlin.com \
    --cc=rosenp@gmail.com \
    --cc=thorsten.blum@linux.dev \
    --cc=tomi.valkeinen@ideasonboard.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