From: Justin Stitt <justinstitt@google.com>
To: Bill Wendling <morbo@google.com>
Cc: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
codemender-patching+linux@google.com
Subject: Re: [PATCH] gpiolib: annotate struct acpi_gpio_mapping with __counted_by_ptr
Date: Mon, 5 Oct 2026 02:31:09 -0700 [thread overview]
Message-ID: <asNuMzqz3G-gmIiD@google.com> (raw)
In-Reply-To: <CAGG=3QV2k-nsZHNSuKEixZb+-LcxvhQsG379ghgyOpiDLTJWzw@mail.gmail.com>
Hi,
On Thu, Oct 01, 2026 at 01:04:47PM -0700, Bill Wendling wrote:
> On Thu, Oct 1, 2026 at 12:56 PM Linus Walleij <linusw@kernel.org> wrote:
<snip>
> It's being #included transitively:
>
> In file included from drivers/firmware/efi/libstub/efi-stub-helper.c:12:
> In file included from ./include/linux/efi.h:20:
> In file included from ./include/linux/rtc.h:18:
> In file included from ./include/linux/nvmem-provider.h:16:
> ./include/linux/gpio/consumer.h:670:55: error: use of undeclared
> identifier 'size'; did you
> mean 'ksize'?
> 670 | const struct acpi_gpio_params *data __counted_by_ptr(size);
> | ^~~~
> | ksize
> ././include/linux/compiler_types.h:392:64: note: expanded from macro
> '__counted_by_ptr'
> 392 | #define __counted_by_ptr(member)
> __attribute__((__counted_by__(member)))
> |
> ^~~~~~
> ./include/linux/slab.h:602:8: note: 'ksize' declared here
> 602 | size_t ksize(const void *objp);
> | ^
>
I wonder if we could have a better warning here guiding you towards
-fexperimental-late-parse-attributes?
Thanks
Justin
next prev parent reply other threads:[~2026-10-05 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 6:38 [PATCH] gpiolib: annotate struct acpi_gpio_mapping with __counted_by_ptr Bill Wendling
2026-09-28 7:22 ` Bill Wendling
2026-10-01 19:56 ` Linus Walleij
2026-10-01 20:04 ` Bill Wendling
2026-10-01 21:24 ` Linus Walleij
2026-10-02 7:38 ` Ard Biesheuvel
2026-10-02 12:44 ` Bill Wendling
2026-10-02 13:51 ` Ard Biesheuvel
2026-10-03 8:54 ` Bill Wendling
2026-10-03 9:10 ` Ard Biesheuvel
2026-10-05 9:31 ` Justin Stitt [this message]
2026-10-05 10:26 ` Bill Wendling
2026-10-07 11:19 ` Linus Walleij
2026-10-08 20:18 ` Bill Wendling
2026-10-02 12:42 ` [PATCH v2] " Bill Wendling
2026-10-02 12:55 ` sashiko-bot
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=asNuMzqz3G-gmIiD@google.com \
--to=justinstitt@google.com \
--cc=brgl@kernel.org \
--cc=codemender-patching+linux@google.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morbo@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 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.