From: Lukas Wunner <lukas@wunner.de>
To: Saravana Kannan <saravanak@google.com>
Cc: Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Android Kernel Team <kernel-team@android.com>,
linux-spi <linux-spi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: Fix spi device unregister flow
Date: Tue, 4 May 2021 11:17:54 +0200 [thread overview]
Message-ID: <20210504091754.GA22045@wunner.de> (raw)
In-Reply-To: <CAGETcx_Z9kjzjTaNUBgKNte8UZcT5HJ5tjkmRmFqddy78Nj9Qw@mail.gmail.com>
On Mon, May 03, 2021 at 11:15:50AM -0700, Saravana Kannan wrote:
> On Mon, May 3, 2021 at 10:56 AM Lukas Wunner <lukas@wunner.de> wrote:
> > Without your patch:
> >
> > spi_unregister_device()
> > device_unregister()
> > device_del()
> > bus_remove_device()
> > device_release_driver() # access to physical SPI device in ->remove()
> > put_device()
> > kobject_put()
> > kref_put()
> > kobject_release()
> > kobject_cleanup()
> > device_release()
> > spidev_release()
> > spi->controller->cleanup() # controller_state freed
> >
> > With your patch:
> >
> > spi_unregister_device()
> > spi_cleanup()
> > spi->controller->cleanup() # controller_state freed
> > device_unregister()
> > device_del()
> > bus_remove_device()
> > device_release_driver() # access to physical SPI device in ->remove()
[...]
> So, it looks like the fix is simple. We just need to move
> spi_cleanup() to the bottom of spi_unregister_device(). I'll send a
> patch for that rather than reverting this and bringing back the other
> bugs.
That would result in a use-after-free if the call to device_unregister()
indeed releases the last ref to the spi_device (which I'd expect is
usually the case).
However, something like this might work (in spi_unregister_device()):
device_del(&spi->dev);
spi_cleanup(spi);
put_device(&spi->dev);
Thanks,
Lukas
prev parent reply other threads:[~2021-05-04 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 23:56 [PATCH] spi: Fix spi device unregister flow Saravana Kannan
2021-04-27 6:52 ` Andy Shevchenko
2021-04-27 10:48 ` Mark Brown
2021-04-27 11:42 ` Andy Shevchenko
2021-04-27 11:49 ` Greg Kroah-Hartman
2021-04-27 15:02 ` Saravana Kannan
2021-04-28 16:53 ` Mark Brown
2021-05-03 10:07 ` Lukas Wunner
2021-05-03 10:16 ` Andy Shevchenko
2021-05-03 17:21 ` Saravana Kannan
2021-05-03 17:56 ` Lukas Wunner
2021-05-03 18:15 ` Saravana Kannan
2021-05-04 9:17 ` Lukas Wunner [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=20210504091754.GA22045@wunner.de \
--to=lukas@wunner.de \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=m.szyprowski@samsung.com \
--cc=rafael@kernel.org \
--cc=saravanak@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;
as well as URLs for NNTP newsgroup(s).