From: Jonathan Cameron <jic23@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: andy@kernel.org, dlechner@baylibre.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
nuno.sa@analog.com, tomislav.denis@avl.com,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ti-ads131e08: Fix trigger reference leak in ads131e08_probe()
Date: Thu, 17 Sep 2026 01:28:36 +0100 [thread overview]
Message-ID: <20260917012836.444a54ef@jic23-hlaptop> (raw)
In-Reply-To: <20260916162114.2083166-1-vulab@iscas.ac.cn>
On Wed, 16 Sep 2026 16:21:14 +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. If
> devm_iio_triggered_buffer_setup() fails before setting that mode, the
> reference acquired for indio_dev->trig leaks. Move the
> iio_trigger_get() after the buffer setup succeeds.
>
> Fixes: d935eddd2799 ("iio: adc: Add driver for Texas Instruments ADS131E0x ADC family")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
Not this solution. See other threads on this.
> ---
> drivers/iio/adc/ti-ads131e08.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/ti-ads131e08.c b/drivers/iio/adc/ti-ads131e08.c
> index a585621b0bc3..d976214504c3 100644
> --- a/drivers/iio/adc/ti-ads131e08.c
> +++ b/drivers/iio/adc/ti-ads131e08.c
> @@ -851,8 +851,6 @@ static int ads131e08_probe(struct spi_device *spi)
> return ret;
> }
>
> - indio_dev->trig = iio_trigger_get(st->trig);
> -
> ret = devm_iio_triggered_buffer_setup(&spi->dev, indio_dev,
> NULL, &ads131e08_trigger_handler, NULL);
> if (ret) {
> @@ -860,6 +858,8 @@ static int ads131e08_probe(struct spi_device *spi)
> return ret;
> }
>
> + indio_dev->trig = iio_trigger_get(st->trig);
> +
> st->vref_reg = devm_regulator_get_optional(&spi->dev, "vref");
> if (!IS_ERR(st->vref_reg)) {
> ret = regulator_enable(st->vref_reg);
prev parent reply other threads:[~2026-09-17 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 16:21 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=20260917012836.444a54ef@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=stable@vger.kernel.org \
--cc=tomislav.denis@avl.com \
--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®