mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, srinivas.pandruvada@linux.intel.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] iio: accel: kxcjk-1013: Fix trigger reference leak in kxcjk1013_probe()
Date: Thu, 17 Sep 2026 01:20:32 +0100	[thread overview]
Message-ID: <20260917012032.5d5f84be@jic23-hlaptop> (raw)
In-Reply-To: <20260916161054.2082486-1-vulab@iscas.ac.cn>

On Wed, 16 Sep 2026 16:10:54 +0000
Wentao Liang <vulab@iscas.ac.cn> wrote:

> The reference acquired for indio_dev->trig is only dropped by
> iio_dev_release() when INDIO_BUFFER_TRIGGERED is set. Move the
> iio_trigger_get() after iio_triggered_buffer_setup() succeeds so that
> failure of motion trigger registration or buffer setup, which return
> before the mode is set, no longer leak the trigger reference.
> 
> Fixes: c1288b833881 ("iio: accel: kxcjk-1013: Increment ref counter for indio_dev->trig")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>

See bma220 reply. Not something we are going to fix like this.

> ---
>  drivers/iio/accel/kxcjk-1013.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/iio/accel/kxcjk-1013.c b/drivers/iio/accel/kxcjk-1013.c
> index 2823ddde4bf2..dbaa829a98c2 100644
> --- a/drivers/iio/accel/kxcjk-1013.c
> +++ b/drivers/iio/accel/kxcjk-1013.c
> @@ -1488,10 +1488,6 @@ static int kxcjk1013_probe(struct i2c_client *client)
>  		if (ret)
>  			goto err_poweroff;
>  
> -		indio_dev->trig = iio_trigger_get(data->dready_trig);
> -
> -		data->motion_trig->ops = &kxcjk1013_trigger_ops;
> -		iio_trigger_set_drvdata(data->motion_trig, indio_dev);
>  		ret = iio_trigger_register(data->motion_trig);
>  		if (ret) {
>  			data->motion_trig = NULL;
> @@ -1508,6 +1504,9 @@ static int kxcjk1013_probe(struct i2c_client *client)
>  		goto err_trigger_unregister;
>  	}
>  
> +	if (data->dready_trig)
> +		indio_dev->trig = iio_trigger_get(data->dready_trig);
> +
>  	ret = pm_runtime_set_active(&client->dev);
>  	if (ret)
>  		goto err_buffer_cleanup;


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 16:10 Wentao Liang
2026-09-17  0:20 ` 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=20260917012032.5d5f84be@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=srinivas.pandruvada@linux.intel.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®