From: Wentao Liang <vulab@iscas.ac.cn>
To: Jianping.Shen@de.bosch.com
Cc: andy@kernel.org, dlechner@baylibre.com, jic23@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
nuno.sa@analog.com, Wentao Liang <vulab@iscas.ac.cn>
Subject: [PATCH] iio: imu: smi330: Fix trigger reference leak in smi330_core_probe()
Date: Wed, 16 Sep 2026 16:32:50 +0000 [thread overview]
Message-ID: <20260916163250.2083963-1-vulab@iscas.ac.cn> (raw)
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: 6f3d8de8886d ("iio: imu: smi330: Add driver")
Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
---
drivers/iio/imu/smi330/smi330_core.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/imu/smi330/smi330_core.c b/drivers/iio/imu/smi330/smi330_core.c
index 7ec5ae7f521a..6bd735c6b61a 100644
--- a/drivers/iio/imu/smi330/smi330_core.c
+++ b/drivers/iio/imu/smi330/smi330_core.c
@@ -886,9 +886,6 @@ int smi330_core_probe(struct device *dev, struct regmap *regmap)
if (ret)
return dev_err_probe(dev, ret,
"IIO register trigger failed\n");
-
- /* Set default operation mode to data ready. */
- indio_dev->trig = iio_trigger_get(data->trig);
}
ret = devm_iio_triggered_buffer_setup(dev, indio_dev,
@@ -897,6 +894,11 @@ int smi330_core_probe(struct device *dev, struct regmap *regmap)
if (ret)
return dev_err_probe(dev, ret, "IIO buffer setup failed\n");
+ if (data->trig) {
+ /* Set default operation mode to data ready. */
+ indio_dev->trig = iio_trigger_get(data->trig);
+ }
+
ret = devm_iio_device_register(dev, indio_dev);
if (ret)
return dev_err_probe(dev, ret, "Register IIO device failed\n");
--
2.34.1
next reply other threads:[~2026-09-16 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 16:32 Wentao Liang [this message]
2026-09-17 0:35 ` Jonathan Cameron
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=20260916163250.2083963-1-vulab@iscas.ac.cn \
--to=vulab@iscas.ac.cn \
--cc=Jianping.Shen@de.bosch.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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®