From: Lee Jones <lee@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: linusw@kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, pavel@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] leds: netxbig: Fix platform device reference leak on successful probe
Date: Tue, 22 Sep 2026 17:03:23 +0100 [thread overview]
Message-ID: <20260922160323.GB3438784@google.com> (raw)
In-Reply-To: <20260917093641.2144866-1-vulab@iscas.ac.cn>
On Thu, 17 Sep 2026, Wentao Liang wrote:
> of_find_device_by_node() returns the GPIO extension device with an
> elevated reference count. The error paths release it through the
> put_device label, but the success path returns directly, so the
> reference is leaked whenever the LED driver probes successfully.
>
> Let the success path fall through to the put_device label.
>
> Fixes: 9af512e81964 ("leds: netxbig: Convert to use GPIO descriptors")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> drivers/leds/leds-netxbig.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/leds/leds-netxbig.c b/drivers/leds/leds-netxbig.c
> index 99df46f2d9f5..d79fee1d9143 100644
> --- a/drivers/leds/leds-netxbig.c
> +++ b/drivers/leds/leds-netxbig.c
> @@ -597,8 +597,7 @@ static int netxbig_leds_get_of_pdata(struct device *dev,
> pdata->leds = leds;
> pdata->num_leds = num_leds;
>
> - return 0;
> -
> + ret = 0;
> put_device:
> put_device(gpio_ext_dev);
> return ret;
Or you could do a nicer clean-up by putting it after last use, then
remove all of the gotos?
--
Lee Jones
prev parent reply other threads:[~2026-09-22 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 9:36 [PATCH] leds: netxbig: Fix platform device reference leak on successful probe Wentao Liang
2026-09-17 9:42 ` sashiko-bot
2026-09-22 16:03 ` Lee Jones [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=20260922160323.GB3438784@google.com \
--to=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.