mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Linus Walleij" <linusw@kernel.org>,
	"Bill Wendling" <morbo@google.com>, "Jeremy Kerr" <jk@ozlabs.org>
Cc: "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: Fri, 02 Oct 2026 09:38:05 +0200	[thread overview]
Message-ID: <7e847715-6bd5-4f69-a9a6-339788810fec@app.fastmail.com> (raw)
In-Reply-To: <CAD++jLnOm3ua7hom_L4YQwN5z81M17WmL_VGqx+-ugrAJ-6_Dg@mail.gmail.com>


On Thu, 1 Oct 2026, at 23:24, Linus Walleij wrote:
> On Thu, Oct 1, 2026 at 10:05 PM Bill Wendling <morbo@google.com> wrote:
>> On Thu, Oct 1, 2026 at 12:56 PM Linus Walleij <linusw@kernel.org> wrote:
>> > On Mon, Sep 28, 2026 at 9:22 AM Bill Wendling <morbo@google.com> wrote:
>> > > On Sun, Sep 27, 2026 at 11:38 PM Bill Wendling <morbo@google.com> wrote:
>> > > >
>> > > > The 'data' pointer field in 'struct acpi_gpio_mapping' is associated
>> > > > with the 'size' field, which represents the number of elements of
>> > > > type 'struct acpi_gpio_params' allocated for 'data'.
>> > > >
>> > > > To improve bounds checking via CONFIG_UBSAN_BOUNDS and
>> > > > CONFIG_FORTIFY_SOURCE, annotate 'data' with the __counted_by_ptr
>> > > > attribute.
>> > > >
>> > > > Analysis of allocation, assignment, and access points shows that the
>> > > > pointer is never accessed before the count is set, which guarantees that
>> > > > this annotation is safe and will not cause runtime panics or
>> > > > false-positive bounds checks.
>> > > >
>> > > > Cc: codemender-patching+linux@google.com
>> > > > Assisted-by: LLM
>> > > > Signed-off-by: Bill Wendling <morbo@google.com>
>> > > > ---
>> > > >  include/linux/gpio/consumer.h | 2 +-
>> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
>> > > >
>> > > > diff --git a/include/linux/gpio/consumer.h b/include/linux/gpio/consumer.h
>> > > > index fceeefd5f893..2b80cf7aa7e7 100644
>> > > > --- a/include/linux/gpio/consumer.h
>> > > > +++ b/include/linux/gpio/consumer.h
>> > > > @@ -667,7 +667,7 @@ struct acpi_gpio_params {
>> > > >
>> > > >  struct acpi_gpio_mapping {
>> > > >         const char *name;
>> > > > -       const struct acpi_gpio_params *data;
>> > > > +       const struct acpi_gpio_params *data __counted_by_ptr(size);
>> > > >         unsigned int size;
>> > > >
>> > > >  /* Ignore IoRestriction field */
>> > >
>> > > There's a problem with 'drivers/firmware/efi/libstub/Makefile'. Clang
>> > > needs a compiler flag to support the "__counted_by_ptr" attribute
>> > > referencing a field *after* the pointer, like in this patch. However,
>> > > the Makefile blasts the flag away for x86 platforms. Below is a hack
>> > > that copies the part of the top-level Makefile that adds the flag. I
>> > > don't think that's a good solution. The comment in the driver's
>> > > Makefile says that the stub code executes before the kernel does,
>> > > which I assume is why a lot of the flags are blown away... In any
>> > > event, I'm not sure how best to address this.
>> >
>> > But is this a problem with the current patch?
>> >
>> > Does libefistub use <linux/gpio/consumer.h> in any way, shape
>> > or form?
>> >
>> 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);
>>       |        ^
>
> Hm I see.
>
> Certainly Jeremy or Ard will have an idea about how to solve this,
> so paging them in.
>

libstub code never executes in the context of the kernel, but only in
the context of the boot firmware. Generally, we disable instrumentation
there that has a significant runtime component, basically because we
cannot crash or panic the kernel before we have even booted it.

Can we just #define __counted_by_ptr(...) to nothing when building
from that Makefile?


  reply	other threads:[~2026-10-02  7:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  6:38 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 [this message]
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
2026-10-05 10:26         ` Bill Wendling
2026-10-02 12:42 ` [PATCH v2] " Bill Wendling

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=7e847715-6bd5-4f69-a9a6-339788810fec@app.fastmail.com \
    --to=ardb@kernel.org \
    --cc=brgl@kernel.org \
    --cc=codemender-patching+linux@google.com \
    --cc=gustavoars@kernel.org \
    --cc=jk@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®