From: Kent Gibson <warthog618@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bamvor Jian Zhang <bamv2005@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/1] gpio: mockup: Convert to use software nodes
Date: Tue, 5 Oct 2021 17:27:53 +0800 [thread overview]
Message-ID: <20211005092753.GA911482@sol> (raw)
In-Reply-To: <20211005091016.18519-1-andriy.shevchenko@linux.intel.com>
On Tue, Oct 05, 2021 at 12:10:16PM +0300, Andy Shevchenko wrote:
> The gpio-mockup driver creates a properties that are shared between
> platform and GPIO devices. Because of that, the properties may not
> be removed at the proper point of time without provoking use-after-free
> as shown in the backtrace:
>
> refcount_t: underflow; use-after-free.
> WARNING: CPU: 0 PID: 103 at lib/refcount.c:28 refcount_warn_saturate+0xd1/0x120
> ...
> Call Trace:
> kobject_put+0xdc/0xf0
> software_node_notify_remove+0xa8/0xc0
> device_del+0x15a/0x3e0
>
> That's why the driver has to manage lifetime of the software nodes by itself.
>
> The problem originates by the old device_add_properties() API, but has been
> only revealed after the commit 5aeb05b27f81 ("software node: balance refcount
> for managed software nodes"). Hence, it's used as landmark for the backporting.
>
> Fixes: 5aeb05b27f81 ("software node: balance refcount for managed software nodes")
Shouldn't that be:
Fixes: bd1e336aa853 ("driver core: platform: Remove platform_device_add_properties()")
> Reported-by: Kent Gibson <warthog618@gmail.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Other than that, looks good and works for me.
Tested-by: Kent Gibson <warthog618@gmail.com>
Cheers,
Kent.
> ---
> drivers/gpio/gpio-mockup.c | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpio/gpio-mockup.c b/drivers/gpio/gpio-mockup.c
> index 0a9d746a0fe0..8b147b565e92 100644
> --- a/drivers/gpio/gpio-mockup.c
> +++ b/drivers/gpio/gpio-mockup.c
> @@ -478,8 +478,18 @@ static void gpio_mockup_unregister_pdevs(void)
> {
> int i;
>
> - for (i = 0; i < GPIO_MOCKUP_MAX_GC; i++)
> - platform_device_unregister(gpio_mockup_pdevs[i]);
> + for (i = 0; i < GPIO_MOCKUP_MAX_GC; i++) {
> + struct platform_device *pdev;
> + struct fwnode_handle *fwnode;
> +
> + pdev = gpio_mockup_pdevs[i];
> + if (!pdev)
> + continue;
> +
> + fwnode = dev_fwnode(&pdev->dev);
> + platform_device_unregister(pdev);
> + fwnode_remove_software_node(fwnode);
> + }
> }
>
> static __init char **gpio_mockup_make_line_names(const char *label,
> @@ -508,6 +518,7 @@ static int __init gpio_mockup_register_chip(int idx)
> struct property_entry properties[GPIO_MOCKUP_MAX_PROP];
> struct platform_device_info pdevinfo;
> struct platform_device *pdev;
> + struct fwnode_handle *fwnode;
> char **line_names = NULL;
> char chip_label[32];
> int prop = 0, base;
> @@ -536,13 +547,18 @@ static int __init gpio_mockup_register_chip(int idx)
> "gpio-line-names", line_names, ngpio);
> }
>
> + fwnode = fwnode_create_software_node(properties, NULL);
> + if (IS_ERR(fwnode))
> + return PTR_ERR(fwnode);
> +
> pdevinfo.name = "gpio-mockup";
> pdevinfo.id = idx;
> - pdevinfo.properties = properties;
> + pdevinfo.fwnode = fwnode;
>
> pdev = platform_device_register_full(&pdevinfo);
> kfree_strarray(line_names, ngpio);
> if (IS_ERR(pdev)) {
> + fwnode_remove_software_node(fwnode);
> pr_err("error registering device");
> return PTR_ERR(pdev);
> }
> --
> 2.33.0
>
next prev parent reply other threads:[~2021-10-05 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 9:10 [PATCH v1 1/1] gpio: mockup: Convert to use software nodes Andy Shevchenko
2021-10-05 9:27 ` Kent Gibson [this message]
2021-10-05 9:30 ` Andy Shevchenko
2021-10-05 9:34 ` Bartosz Golaszewski
2021-10-05 9:41 ` Andy Shevchenko
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=20211005092753.GA911482@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bamv2005@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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.