From: Jonathan Cameron <jic23@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: andy@kernel.org, apokusinski01@gmail.com, dlechner@baylibre.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
nuno.sa@analog.com, stable@vger.kernel.org
Subject: Re: [PATCH] iio: temperature: tmp006: Fix trigger reference leak in tmp006_probe()
Date: Thu, 17 Sep 2026 01:40:44 +0100 [thread overview]
Message-ID: <20260917014044.4f72b35c@jic23-hlaptop> (raw)
In-Reply-To: <20260916164517.2084799-1-vulab@iscas.ac.cn>
On Wed, 16 Sep 2026 16:45:17 +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. Failure of
> devm_request_irq() or of triggered buffer setup returns before that
> mode is set and leaks the reference acquired for indio_dev->trig.
> Take the reference only after the triggered buffer setup succeeds.
>
> Fixes: 91f75ccf9f03 ("iio: temperature: tmp006: add triggered buffer support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
Not this way - see other threads on same topic.
> ---
> drivers/iio/temperature/tmp006.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/temperature/tmp006.c b/drivers/iio/temperature/tmp006.c
> index d8d8c8936d17..06303ce72bfb 100644
> --- a/drivers/iio/temperature/tmp006.c
> +++ b/drivers/iio/temperature/tmp006.c
> @@ -354,8 +354,6 @@ static int tmp006_probe(struct i2c_client *client)
> if (ret)
> return ret;
>
> - indio_dev->trig = iio_trigger_get(data->drdy_trig);
> -
> ret = devm_request_irq(&client->dev, client->irq,
> iio_trigger_generic_data_rdy_poll,
> IRQF_NO_THREAD, "tmp006_irq",
> @@ -369,6 +367,9 @@ static int tmp006_probe(struct i2c_client *client)
> if (ret < 0)
> return ret;
>
> + if (data->drdy_trig)
> + indio_dev->trig = iio_trigger_get(data->drdy_trig);
> +
> return devm_iio_device_register(&client->dev, indio_dev);
> }
>
prev parent reply other threads:[~2026-09-17 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 16:45 Wentao Liang
2026-09-17 0:40 ` 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=20260917014044.4f72b35c@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=apokusinski01@gmail.com \
--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=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®