From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH v2] gpiolib: Fix triggering "kobject: 'gpiochipX' is not initialized, yet" kobject_get() errors
Date: Wed, 3 Apr 2024 13:05:06 +0200 [thread overview]
Message-ID: <CAMRc=Mcocz5fJUJsjje_2qSRcptv-dx6bWFsaWZNVQs=+n7YKA@mail.gmail.com> (raw)
In-Reply-To: <0303f5f6-05f8-43c7-8922-11de2550d356@redhat.com>
On Wed, Apr 3, 2024 at 10:17 AM Hans de Goede <hdegoede@redhat.com> wrote:
>
> Hi,
>
> On 4/2/24 6:51 PM, Andy Shevchenko wrote:
> > On Tue, Apr 2, 2024 at 7:43 PM Hans de Goede <hdegoede@redhat.com> wrote:
> >>
> >> When a gpiochip gets added by loading a module, then another driver may
> >> be waiting for that gpiochip to load on the deferred-probe list.
> >>
> >> If the deferred-probe for the consumer of gpiochip then triggers between
> >> the gpiodev_add_to_list_unlocked() calls which makes gpio_device_find()
> >> see the chip and the gpiochip_setup_dev() later then gpio_device_find()
> >> does a kobject_get() on an uninitialzed kobject since the kobject is
> >
> > uninitialized
>
> Bartosz, can you fix this up while merging or do you prefer a v3?
>
Yes, queued for fixes.
Bart
prev parent reply other threads:[~2024-04-03 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 16:43 [PATCH v2] gpiolib: Fix triggering "kobject: 'gpiochipX' is not initialized, yet" kobject_get() errors Hans de Goede
2024-04-02 16:51 ` Andy Shevchenko
2024-04-03 8:17 ` Hans de Goede
2024-04-03 11:05 ` Bartosz Golaszewski [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='CAMRc=Mcocz5fJUJsjje_2qSRcptv-dx6bWFsaWZNVQs=+n7YKA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).