linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	syzbot+d27b4c8adbbff70fbfde@syzkaller.appspotmail.com
Subject: Re: [PATCH 1/2] gpio: fix NULL-deref-on-deregistration regression
Date: Mon, 1 Mar 2021 09:44:46 +0100	[thread overview]
Message-ID: <YDypfjoBpHsd+dCo@hovoldconsulting.com> (raw)
In-Reply-To: <CAGETcx-4Q+SkdLO-rXE-zt2kdz=J1cnrPjv07mt0KRtCPa_OGg@mail.gmail.com>

On Fri, Feb 26, 2021 at 01:54:12PM -0800, Saravana Kannan wrote:
> On Fri, Feb 26, 2021 at 6:55 AM Johan Hovold <johan@kernel.org> wrote:
> >
> > Fix a NULL-pointer deference when deregistering the gpio character
> > device that was introduced by the recent stub-driver hack. When the new
> > "driver" is unbound as part of deregistration, driver core clears the
> > driver-data pointer which is used to retrieve the struct gpio_device in
> > its release callback.
> >
> > Fix this by using container_of() in the release callback as should have
> > been done all along.
> >
> > Fixes: 4731210c09f5 ("gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by default")
> > Cc: Saravana Kannan <saravanak@google.com>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Reported-by: syzbot+d27b4c8adbbff70fbfde@syzkaller.appspotmail.com
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> > ---
> >  drivers/gpio/gpiolib.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index adf55db080d8..e1016bc8cf14 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -474,7 +474,7 @@ EXPORT_SYMBOL_GPL(gpiochip_line_is_valid);
> >
> >  static void gpiodevice_release(struct device *dev)
> >  {
> > -       struct gpio_device *gdev = dev_get_drvdata(dev);
> > +       struct gpio_device *gdev = container_of(dev, struct gpio_device, dev);
> 
> Can you also delete the dev_set_drvdata() in
> gpiochip_add_data_with_key() if the drvdata is not used
> elsewhere anymore? I skimmed the code and it doesn't look like it, but
> I could be wrong.

Yeah, I considered it but didn't want to risk introducing any new
regressions just to clean up a redundant store.

But looking at it again today, I agree that it looks like it isn't used
anywhere else. I'll send a v2. Thanks.

Johan

  reply	other threads:[~2021-03-01  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 14:52 [PATCH 0/2] gpio: regression fixes Johan Hovold
2021-02-26 14:52 ` [PATCH 1/2] gpio: fix NULL-deref-on-deregistration regression Johan Hovold
2021-02-26 21:54   ` Saravana Kannan
2021-03-01  8:44     ` Johan Hovold [this message]
2021-02-26 14:52 ` [PATCH 2/2] gpio: fix gpio-device list corruption Johan Hovold
2021-02-26 20:59   ` Saravana Kannan

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=YDypfjoBpHsd+dCo@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saravanak@google.com \
    --cc=syzbot+d27b4c8adbbff70fbfde@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).