From: Jonathan Cameron <jic23@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: Michael.Hennerich@analog.com, andy@kernel.org,
cosmin.tanislav@analog.com, dlechner@baylibre.com,
lars@metafoo.de, linusw@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, nuno.sa@analog.com,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: addac: ad74413r: Fix trigger reference leak in ad74413r_probe()
Date: Thu, 17 Sep 2026 01:28:59 +0100 [thread overview]
Message-ID: <20260917012859.4007a80b@jic23-hlaptop> (raw)
In-Reply-To: <20260916162251.2083286-1-vulab@iscas.ac.cn>
On Wed, 16 Sep 2026 16:22:51 +0000
Wentao Liang <vulab@iscas.ac.cn> wrote:
> The reference taken with iio_trigger_get() is only dropped by
> iio_dev_release() when INDIO_BUFFER_TRIGGERED is set. Every failure
> between trigger registration and the triggered buffer setup returns
> before that mode is set and leaks the reference acquired for
> indio_dev->trig. Move the iio_trigger_get() after the buffer setup
> succeeds.
>
> Fixes: fea251b6a5db ("iio: addac: add AD74413R driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
Not this solution. For anyone interested see other replies to similar patches.
> ---
> drivers/iio/addac/ad74413r.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/addac/ad74413r.c b/drivers/iio/addac/ad74413r.c
> index fe930ce5ee30..380900bf6772 100644
> --- a/drivers/iio/addac/ad74413r.c
> +++ b/drivers/iio/addac/ad74413r.c
> @@ -1397,7 +1397,6 @@ static int ad74413r_probe(struct spi_device *spi)
> indio_dev->name = st->chip_info->name;
> indio_dev->modes = INDIO_DIRECT_MODE;
> indio_dev->info = &ad74413r_info;
> - indio_dev->trig = iio_trigger_get(st->trig);
>
> ret = ad74413r_reset(st);
> if (ret)
> @@ -1467,6 +1466,8 @@ static int ad74413r_probe(struct spi_device *spi)
> if (ret)
> return ret;
>
> + indio_dev->trig = iio_trigger_get(st->trig);
> +
> return devm_iio_device_register(st->dev, indio_dev);
> }
>
prev parent reply other threads:[~2026-09-17 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 16:22 Wentao Liang
2026-09-17 0:28 ` Jonathan Cameron [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=20260917012859.4007a80b@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=cosmin.tanislav@analog.com \
--cc=dlechner@baylibre.com \
--cc=lars@metafoo.de \
--cc=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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®