linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Kennington <wak@google.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] spi: Fix use-after-free with devm_spi_alloc_*
Date: Fri, 9 Apr 2021 02:05:05 -0700	[thread overview]
Message-ID: <CAPnigKnV+=X9jn+iD2-DemfujRobANcL1NztXQjp_PeGbkWejw@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VcRE3JOyFEMzvP9RW1du3cXx3zaTq-8KJnGt9zaJeiJZg@mail.gmail.com>

For the header file comment? I think it's actually backwards since
`devm_allocated = true` would indicate the device is managed with
devres. Should I send a followup change or v2?


On Fri, Apr 9, 2021 at 12:20 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
>
>
> On Wednesday, April 7, 2021, William A. Kennington III <wak@google.com> wrote:
>>
>> We can't rely on the contents of the devres list during
>> spi_unregister_controller(), as the list is already torn down at the
>> time we perform devres_find() for devm_spi_release_controller. This
>> causes devices registered with devm_spi_alloc_{master,slave}() to be
>> mistakenly identified as legacy, non-devm managed devices and have their
>> reference counters decremented below 0.
>>
>> ------------[ cut here ]------------
>> WARNING: CPU: 1 PID: 660 at lib/refcount.c:28 refcount_warn_saturate+0x108/0x174
>> [<b0396f04>] (refcount_warn_saturate) from [<b03c56a4>] (kobject_put+0x90/0x98)
>> [<b03c5614>] (kobject_put) from [<b0447b4c>] (put_device+0x20/0x24)
>>  r4:b6700140
>> [<b0447b2c>] (put_device) from [<b07515e8>] (devm_spi_release_controller+0x3c/0x40)
>> [<b07515ac>] (devm_spi_release_controller) from [<b045343c>] (release_nodes+0x84/0xc4)
>>  r5:b6700180 r4:b6700100
>> [<b04533b8>] (release_nodes) from [<b0454160>] (devres_release_all+0x5c/0x60)
>>  r8:b1638c54 r7:b117ad94 r6:b1638c10 r5:b117ad94 r4:b163dc10
>> [<b0454104>] (devres_release_all) from [<b044e41c>] (__device_release_driver+0x144/0x1ec)
>>  r5:b117ad94 r4:b163dc10
>> [<b044e2d8>] (__device_release_driver) from [<b044f70c>] (device_driver_detach+0x84/0xa0)
>>  r9:00000000 r8:00000000 r7:b117ad94 r6:b163dc54 r5:b1638c10 r4:b163dc10
>> [<b044f688>] (device_driver_detach) from [<b044d274>] (unbind_store+0xe4/0xf8)
>>
>> Instead, determine the devm allocation state as a flag on the
>> controller which is guaranteed to be stable during cleanup.
>>
>> Fixes: 5e844cc37a5c ("spi: Introduce device-managed SPI controller allocation")
>> Signed-off-by: William A. Kennington III <wak@google.com>
>> ---
>>  drivers/spi/spi.c       | 9 ++-------
>>  include/linux/spi/spi.h | 3 +++
>>  2 files changed, 5 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
>> index b08efe88ccd6..904a353798b6 100644
>> --- a/drivers/spi/spi.c
>> +++ b/drivers/spi/spi.c
>> @@ -2496,6 +2496,7 @@ struct spi_controller *__devm_spi_alloc_controller(struct device *dev,
>>
>>         ctlr = __spi_alloc_controller(dev, size, slave);
>>         if (ctlr) {
>> +               ctlr->devm_allocated = true;
>>                 *ptr = ctlr;
>>                 devres_add(dev, ptr);
>>         } else {
>> @@ -2842,11 +2843,6 @@ int devm_spi_register_controller(struct device *dev,
>>  }
>>  EXPORT_SYMBOL_GPL(devm_spi_register_controller);
>>
>> -static int devm_spi_match_controller(struct device *dev, void *res, void *ctlr)
>> -{
>> -       return *(struct spi_controller **)res == ctlr;
>> -}
>> -
>>  static int __unregister(struct device *dev, void *null)
>>  {
>>         spi_unregister_device(to_spi_device(dev));
>> @@ -2893,8 +2889,7 @@ void spi_unregister_controller(struct spi_controller *ctlr)
>>         /* Release the last reference on the controller if its driver
>>          * has not yet been converted to devm_spi_alloc_master/slave().
>>          */
>> -       if (!devres_find(ctlr->dev.parent, devm_spi_release_controller,
>> -                        devm_spi_match_controller, ctlr))
>> +       if (!ctlr->devm_allocated)
>>                 put_device(&ctlr->dev);
>>
>>         /* free bus id */
>> diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
>> index 592897fa4f03..643139b1eafe 100644
>> --- a/include/linux/spi/spi.h
>> +++ b/include/linux/spi/spi.h
>> @@ -510,6 +510,9 @@ struct spi_controller {
>>
>>  #define SPI_MASTER_GPIO_SS             BIT(5)  /* GPIO CS must select slave */
>>
>> +       /* flag indicating this is a non-devres managed controller */
>
>
>
> Isn’t “non-“ part confusing a lot?
>
>>
>> +       bool                    devm_allocated;
>> +
>>         /* flag indicating this is an SPI slave controller */
>>         bool                    slave;
>>
>> --
>> 2.31.0.208.g409f899ff0-goog
>>
>
>
> --
> With Best Regards,
> Andy Shevchenko
>
>

      parent reply	other threads:[~2021-04-09  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  9:55 [PATCH] spi: Fix use-after-free with devm_spi_alloc_* William A. Kennington III
2021-04-08 13:11 ` Mark Brown
2021-04-08 16:54 ` Mark Brown
2021-04-09  6:59 ` Joel Stanley
     [not found] ` <CAHp75VcRE3JOyFEMzvP9RW1du3cXx3zaTq-8KJnGt9zaJeiJZg@mail.gmail.com>
2021-04-09  9:05   ` William Kennington [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='CAPnigKnV+=X9jn+iD2-DemfujRobANcL1NztXQjp_PeGbkWejw@mail.gmail.com' \
    --to=wak@google.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=broonie@kernel.org \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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 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).