Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: Michael.Hennerich@analog.com, andy@kernel.org,
	dlechner@baylibre.com, lars@metafoo.de,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	nuno.sa@analog.com, stefan.popa@analog.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7606: Fix trigger reference leak in ad7606_probe()
Date: Thu, 17 Sep 2026 01:26:05 +0100	[thread overview]
Message-ID: <20260917012605.690b430e@jic23-hlaptop> (raw)
In-Reply-To: <20260916161454.2082753-1-vulab@iscas.ac.cn>

On Wed, 16 Sep 2026 16:14:54 +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_request_threaded_irq() or triggered buffer setup fails, probe
> returns before the mode is set and the trigger reference leaks. Move
> the iio_trigger_get() after those setup steps succeed.
> 
> Fixes: cc49bd1652a4 ("staging: iio: adc: ad7606: Add support for threaded irq")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
As in bma220 though slightly different reasoning.

No to this as too magic to rely on ordering. Needs a better fix with
the registration state transitions handle in the iio core. There
should be no such ordering constraint.

Jonathan

> ---
>  drivers/iio/adc/ad7606.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/adc/ad7606.c b/drivers/iio/adc/ad7606.c
> index d9271894f091..2deef474001b 100644
> --- a/drivers/iio/adc/ad7606.c
> +++ b/drivers/iio/adc/ad7606.c
> @@ -1638,8 +1638,6 @@ int ad7606_probe(struct device *dev, int irq, void __iomem *base_address,
>  		if (ret)
>  			return ret;
>  
> -		indio_dev->trig = iio_trigger_get(st->trig);
> -
>  		ret = devm_request_threaded_irq(dev, irq, NULL, &ad7606_interrupt,
>  						IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
>  						chip_info->name, indio_dev);
> @@ -1652,6 +1650,8 @@ int ad7606_probe(struct device *dev, int irq, void __iomem *base_address,
>  						      &ad7606_buffer_ops);
>  		if (ret)
>  			return ret;
> +
> +		indio_dev->trig = iio_trigger_get(st->trig);
>  	}
>  
>  	st->write_scale = ad7606_write_scale_hw;


      reply	other threads:[~2026-09-17  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 16:14 [PATCH] iio: adc: ad7606: Fix trigger reference leak in ad7606_probe() Wentao Liang
2026-09-17  0:26 ` 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=20260917012605.690b430e@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=stable@vger.kernel.org \
    --cc=stefan.popa@analog.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