mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Ashwin Gundarapu <linuxuser509@zohomail.in>
Cc: "linux-iio" <linux-iio@vger.kernel.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: trigger: fix memory leak in viio_trigger_alloc()
Date: Fri, 22 May 2026 13:02:18 +0100	[thread overview]
Message-ID: <20260522130218.4f34ff65@jic23-huawei> (raw)
In-Reply-To: <19e4f819ed9.2157dac799522.5155742748768717789@zohomail.in>

On Fri, 22 May 2026 17:15:55 +0530
Ashwin Gundarapu <linuxuser509@zohomail.in> wrote:

> From: Ashwin Gundarapu <linuxuser509@zohomail.in>
> Date: Fri, 22 May 2026 17:11:00 +0530
> Subject: [PATCH] iio: trigger: fix memory leak in viio_trigger_alloc()
> 
> Separate error paths for before/after device_initialize().
> 
> The free_trig label was used for both early errors (before
> device_initialize) and late errors (after device_initialize).
> 
> Replace the unified kfree() with:
> - kfree() for early errors (free_trig)
> - put_device() for late errors (free_descs)
> 
> This prevents put_device() on an uninitialized device and
> ensures proper reference counting cleanup.
> 
> Signed-off-by: Ashwin Gundarapu <linuxuser509@zohomail.in>
Even for a simple fix, wait longer between iterations.

As I just replied to v1, your tree is old. This won't even apply
and the bug has been correctly fixed in upstream.

> ---
>  drivers/iio/industrialio-trigger.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/industrialio-trigger.c b/drivers/iio/industrialio-trigger.c
> index 9c72e7ae996c..39208c65e6c1 100644
> --- a/drivers/iio/industrialio-trigger.c
> +++ b/drivers/iio/industrialio-trigger.c
> @@ -597,9 +597,11 @@ struct iio_trigger *viio_trigger_alloc(struct device *parent,
>  
>  free_descs:
>  	irq_free_descs(trig->subirq_base, CONFIG_IIO_CONSUMERS_PER_TRIGGER);
> -free_trig:
>  	put_device(&trig->dev);
>  	return NULL;
> +free_trig:
> +	kfree(trig);
> +	return NULL;
>  }
>  
>  /**
> --
> 2.43.0
> 
> 
> 


  reply	other threads:[~2026-05-22 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 11:45 Ashwin Gundarapu
2026-05-22 12:02 ` Jonathan Cameron [this message]
2026-05-22 12:06 ` Joshua Crofts

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=20260522130218.4f34ff65@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxuser509@zohomail.in \
    /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®