From: Joshua Crofts <joshua.crofts1@gmail.com>
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Kees Cook" <kees@kernel.org>,
"Daniel Baluta" <daniel.baluta@intel.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: dummy: free software device on configfs release
Date: Mon, 14 Sep 2026 15:42:04 +0200 [thread overview]
Message-ID: <20260914154204.000028fa@gmail.com> (raw)
In-Reply-To: <20260914115404.1691763-1-lgs201920130244@gmail.com>
On Mon, 14 Sep 2026 19:54:04 +0800
Guangshuo Li <lgs201920130244@gmail.com> wrote:
> iio_dummy_probe() allocates struct iio_sw_device with kzalloc_obj().
> The error paths free it, but after successful registration the normal
> removal path only frees the contained IIO device, leaving the software
> device allocation behind.
>
> The software device embeds a config_group. device_drop_group() calls
> iio_sw_device_destroy() and then drops the config_item reference with
> config_item_put(). Therefore, freeing the software device directly from
> iio_dummy_remove() would free the embedded config_item before that
> final put.
>
> Configfs requires dynamically allocated config_items to provide a
> release callback which frees the containing object when the reference
> count reaches zero.
>
> Add a release callback to iio_dummy_type and free the software device
> there.
>
> This issue was found by manual code inspection.
>
> Fixes: 3d85fb6f8104 ("iio: dummy: Convert IIO dummy to configfs")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
> drivers/iio/dummy/iio_simple_dummy.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/iio/dummy/iio_simple_dummy.c b/drivers/iio/dummy/iio_simple_dummy.c
> index 19fcdbbc11c6..7d2ff1d4a06e 100644
> --- a/drivers/iio/dummy/iio_simple_dummy.c
> +++ b/drivers/iio/dummy/iio_simple_dummy.c
> @@ -23,7 +23,19 @@
> #include <linux/iio/sw_device.h>
> #include "iio_simple_dummy.h"
>
> +static void iio_dummy_release(struct config_item *item)
> +{
> + struct iio_sw_device *swd = to_iio_sw_device(item);
> +
> + kfree(swd);
> +}
> +
> +static const struct configfs_item_operations iio_dummy_item_ops = {
> + .release = iio_dummy_release,
> +};
> +
> static const struct config_item_type iio_dummy_type = {
> + .ct_item_ops = &iio_dummy_item_ops,
> .ct_owner = THIS_MODULE,
> };
>
Seems legit.
Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
Sashiko also pointed out that the same issue is in industrialio-sw-trigger.c:
https://sashiko.dev/#/patchset/20260914115404.1691763-1-lgs201920130244%40gmail.com
--
Kind regards,
Joshua Crofts
next prev parent reply other threads:[~2026-09-14 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:54 Guangshuo Li
2026-09-14 13:42 ` Joshua Crofts [this message]
2026-09-14 16:08 ` David Lechner
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=20260914154204.000028fa@gmail.com \
--to=joshua.crofts1@gmail.com \
--cc=andy@kernel.org \
--cc=daniel.baluta@intel.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=kees@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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 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®