From: Kent Gibson <warthog618@gmail.com>
To: Herve Codina <herve.codina@bootlin.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 2/2] gpiolib: cdev: release IRQs when the gpio chip device is removed
Date: Thu, 22 Feb 2024 08:57:44 +0800 [thread overview]
Message-ID: <20240222005744.GA3603@rigel> (raw)
In-Reply-To: <20240220142959.GA244726@rigel>
On Tue, Feb 20, 2024 at 10:29:59PM +0800, Kent Gibson wrote:
> On Tue, Feb 20, 2024 at 12:10:18PM +0100, Herve Codina wrote:
...
> > }
> >
> > +static int linereq_unregistered_notify(struct notifier_block *nb,
> > + unsigned long action, void *data)
> > +{
> > + struct linereq *lr = container_of(nb, struct linereq,
> > + device_unregistered_nb);
> > + int i;
> > +
> > + for (i = 0; i < lr->num_lines; i++) {
> > + if (lr->lines[i].desc)
> > + edge_detector_stop(&lr->lines[i]);
> > + }
> > +
>
> Firstly, the re-ordering in the previous patch creates a race,
> as the NULLing of the gdev->chip serves to numb the cdev ioctls, so
> there is now a window between the notifier being called and that numbing,
> during which userspace may call linereq_set_config() and re-request
> the irq.
>
> There is also a race here with linereq_set_config(). That can be prevented
> by holding the lr->config_mutex - assuming the notifier is not being called
> from atomic context.
>
It occurs to me that the fixed reordering in patch 1 would place
the notifier call AFTER the NULLing of the ioctls, so there will no longer
be any chance of a race with linereq_set_config() - so holding the
config_mutex semaphore is not necessary.
In which case this patch is fine - it is only patch 1 that requires
updating.
Cheers,
Kent.
next prev parent reply other threads:[~2024-02-22 0:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 11:10 [PATCH 0/2] gpio-cdev: Release IRQ used by gpio-cdev on gpio chip removal Herve Codina
2024-02-20 11:10 ` [PATCH 1/2] gpiolib: call gcdev_unregister() sooner in the removal operations Herve Codina
2024-02-20 13:47 ` Bartosz Golaszewski
2024-02-20 11:10 ` [PATCH 2/2] gpiolib: cdev: release IRQs when the gpio chip device is removed Herve Codina
2024-02-20 14:29 ` Kent Gibson
2024-02-20 18:26 ` Herve Codina
2024-02-21 0:25 ` Kent Gibson
2024-02-21 0:55 ` Kent Gibson
2024-02-22 0:57 ` Kent Gibson [this message]
2024-02-22 1:05 ` Kent Gibson
2024-02-22 8:31 ` Bartosz Golaszewski
2024-02-22 11:36 ` Herve Codina
2024-02-22 12:21 ` Bartosz Golaszewski
2024-02-22 23:51 ` Saravana Kannan
2024-02-27 8:26 ` Herve Codina
2024-02-27 19:27 ` Bartosz Golaszewski
2024-02-20 13:41 ` [PATCH 0/2] gpio-cdev: Release IRQ used by gpio-cdev on gpio chip removal Bartosz Golaszewski
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=20240222005744.GA3603@rigel \
--to=warthog618@gmail.com \
--cc=brgl@bgdev.pl \
--cc=herve.codina@bootlin.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=thomas.petazzoni@bootlin.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.