mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: andriy.shevchenko@linux.intel.com, brgl@kernel.org,
	heiko@sntech.de,  linusw@kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	linux-rockchip@lists.infradead.org, ye.zhang@rock-chips.com,
	 stable@vger.kernel.org
Subject: Re: [PATCH] gpio: rockchip: Fix bank clock leak in rockchip_get_bank_data()
Date: Wed, 16 Sep 2026 12:55:15 +0200	[thread overview]
Message-ID: <aqpxJaYqJ5NHG1No@venus> (raw)
In-Reply-To: <20260916102258.2018689-1-vulab@iscas.ac.cn>

[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]

Hi,

On Wed, Sep 16, 2026 at 10:22:58AM +0000, Wentao Liang wrote:
> rockchip_get_bank_data() obtains the bank clock with of_clk_get() and
> enables it before reading the GPIO version ID.  The reference returned
> by of_clk_get() is never dropped on the error paths that follow:
> 
> When the debounce clock is missing, the bank clock is disabled with
> clk_disable_unprepare() but the reference is never released with
> clk_put().  When the version ID is unsupported, the function returns
> -ENODEV leaving the bank clock prepared, enabled and referenced.
> 
> Drop the reference with clk_put() on both error paths and disable and
> unprepare the bank clock on the unsupported version path so that probe
> failures no longer leak the clock.
> 
> Fixes: 41209307cad7 ("gpio: rockchip: change the GPIO version judgment logic")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---

This got fixed in 3e46c18d5d87 ("gpio: rockchip: convert bank->clk
to devm_clk_get_enabled()") and 950007767823 ("gpio: rockchip:
teardown bugs and resource leaks") already. Please make sure to use
latest kernel trees.

Greetings,

-- Sebastian

>  drivers/gpio/gpio-rockchip.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpio/gpio-rockchip.c b/drivers/gpio/gpio-rockchip.c
> index 44d7ebd12724..69a7cd8c9a1a 100644
> --- a/drivers/gpio/gpio-rockchip.c
> +++ b/drivers/gpio/gpio-rockchip.c
> @@ -673,6 +673,7 @@ static int rockchip_get_bank_data(struct rockchip_pin_bank *bank)
>  		if (IS_ERR(bank->db_clk)) {
>  			dev_err(bank->dev, "cannot find debounce clk\n");
>  			clk_disable_unprepare(bank->clk);
> +			clk_put(bank->clk);
>  			return -EINVAL;
>  		}
>  		break;
> @@ -682,6 +683,8 @@ static int rockchip_get_bank_data(struct rockchip_pin_bank *bank)
>  		break;
>  	default:
>  		dev_err(bank->dev, "unsupported version ID: 0x%08x\n", id);
> +		clk_disable_unprepare(bank->clk);
> +		clk_put(bank->clk);
>  		return -ENODEV;
>  	}
>  
> -- 
> 2.34.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-09-16 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 10:22 Wentao Liang
2026-09-16 10:55 ` Sebastian Reichel [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=aqpxJaYqJ5NHG1No@venus \
    --to=sebastian.reichel@collabora.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brgl@kernel.org \
    --cc=heiko@sntech.de \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=vulab@iscas.ac.cn \
    --cc=ye.zhang@rock-chips.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®