From: <Conor.Dooley@microchip.com>
To: <yangyingliang@huawei.com>, <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH] Revert "spi: simplify devm_spi_register_controller"
Date: Wed, 13 Jul 2022 06:37:08 +0000 [thread overview]
Message-ID: <bf2811e4-86f4-140e-2a3d-388d265557c7@microchip.com> (raw)
In-Reply-To: <20220712135504.1055688-1-yangyingliang@huawei.com>
On 12/07/2022 14:55, Yang Yingliang wrote:
> This reverts commit 59ebbe40fb51e307032ae7f63b2749fad2d4635a.
>
> If devm_add_action() fails in devm_add_action_or_reset(),
> devm_spi_unregister() will be called, it decreases the
> refcount of 'ctlr->dev' to 0, then it will cause uaf in
> the drivers that calling spi_put_controller() in error path.
Whether a revert is the right fix or not, this is the same
conclusion I came to reading your patch for my driver & on
that basis:
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Seems like the master variant of this is used over 40 times:
rg "(?s)devm_spi_register_master.*master_put" drivers/spi --multiline -l
>
> Fixes: 59ebbe40fb51 ("spi: simplify devm_spi_register_controller")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> drivers/spi/spi.c | 19 ++++++++++++++-----
> 1 file changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index dc1a324e3271..ef751ccd65be 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -3130,9 +3130,9 @@ int spi_register_controller(struct spi_controller *ctlr)
> }
> EXPORT_SYMBOL_GPL(spi_register_controller);
>
> -static void devm_spi_unregister(void *ctlr)
> +static void devm_spi_unregister(struct device *dev, void *res)
> {
> - spi_unregister_controller(ctlr);
> + spi_unregister_controller(*(struct spi_controller **)res);
> }
>
> /**
> @@ -3151,13 +3151,22 @@ static void devm_spi_unregister(void *ctlr)
> int devm_spi_register_controller(struct device *dev,
> struct spi_controller *ctlr)
> {
> + struct spi_controller **ptr;
> int ret;
>
> + ptr = devres_alloc(devm_spi_unregister, sizeof(*ptr), GFP_KERNEL);
> + if (!ptr)
> + return -ENOMEM;
> +
> ret = spi_register_controller(ctlr);
> - if (ret)
> - return ret;
> + if (!ret) {
> + *ptr = ctlr;
> + devres_add(dev, ptr);
> + } else {
> + devres_free(ptr);
> + }
>
> - return devm_add_action_or_reset(dev, devm_spi_unregister, ctlr);
> + return ret;
> }
> EXPORT_SYMBOL_GPL(devm_spi_register_controller);
>
next prev parent reply other threads:[~2022-07-13 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 13:55 Yang Yingliang
2022-07-13 6:37 ` Conor.Dooley [this message]
2022-07-13 12:42 ` Mark Brown
2022-07-14 2:08 ` Yang Yingliang
2022-07-13 14:19 ` Mark Brown
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=bf2811e4-86f4-140e-2a3d-388d265557c7@microchip.com \
--to=conor.dooley@microchip.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=yangyingliang@huawei.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
all inboxes | Powered by JetHome®