All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: bgolaszewski@baylibre.com, saravanak@google.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] gpio: fix gpio-device list corruption" failed to apply to 5.11-stable tree
Date: Fri, 12 Mar 2021 11:01:47 +0100	[thread overview]
Message-ID: <YEs8C0E6nM4QVBol@kroah.com> (raw)
In-Reply-To: <YEsqnDY7nGWuh9h5@hovoldconsulting.com>

On Fri, Mar 12, 2021 at 09:47:24AM +0100, Johan Hovold wrote:
> On Thu, Mar 11, 2021 at 06:41:41PM +0100, Greg Kroah-Hartman wrote:
> > 
> > The patch below does not apply to the 5.11-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> 
> > ------------------ original commit in Linus's tree ------------------
> > 
> > From cf25ef6b631c6fc6c0435fc91eba8734cca20511 Mon Sep 17 00:00:00 2001
> > From: Johan Hovold <johan@kernel.org>
> > Date: Mon, 1 Mar 2021 10:05:19 +0100
> > Subject: [PATCH] gpio: fix gpio-device list corruption
> > 
> > Make sure to hold the gpio_lock when removing the gpio device from the
> > gpio_devices list (when dropping the last reference) to avoid corrupting
> > the list when there are concurrent accesses.
> > 
> > Fixes: ff2b13592299 ("gpio: make the gpiochip a real device")
> > Cc: stable@vger.kernel.org      # 4.6
> > Reviewed-by: Saravana Kannan <saravanak@google.com>
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> > Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > 
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index 6e0572515d02..4253837f870b 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -475,8 +475,12 @@ EXPORT_SYMBOL_GPL(gpiochip_line_is_valid);
> >  static void gpiodevice_release(struct device *dev)
> >  {
> >  	struct gpio_device *gdev = container_of(dev, struct gpio_device, dev);
> > +	unsigned long flags;
> >  
> > +	spin_lock_irqsave(&gpio_lock, flags);
> >  	list_del(&gdev->list);
> > +	spin_unlock_irqrestore(&gpio_lock, flags);
> > +
> >  	ida_free(&gpio_ida, gdev->id);
> >  	kfree_const(gdev->label);
> >  	kfree(gdev->descs);
> > 
> 
> Bah, that's because of a6112998ee45 ("gpio: fix
> NULL-deref-on-deregistration regression") which is strictly only needed
> in 5.12 even if it could be backported (the commit message might be a
> bit confusing though).
> 
> I should have reversed the order of these two.
> 
> Below is a backport to 5.11.

Thanks for the backport, also added to 5.10.y

greg k-h

  reply	other threads:[~2021-03-12 10:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 17:41 FAILED: patch "[PATCH] gpio: fix gpio-device list corruption" failed to apply to 5.11-stable tree gregkh
2021-03-12  8:47 ` Johan Hovold
2021-03-12 10:01   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-11 18:16 gregkh

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=YEs8C0E6nM4QVBol@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=johan@kernel.org \
    --cc=saravanak@google.com \
    --cc=stable@vger.kernel.org \
    /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.