mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Breathitt Gray <wbg@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: William Breathitt Gray <wbg@kernel.org>,
	david@lechnology.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] counter: ti-eqep: fix refcount leak in ti_eqep_probe()
Date: Mon, 17 Aug 2026 14:15:43 -0400	[thread overview]
Message-ID: <20260817181545.190769-1-wbg@kernel.org> (raw)
In-Reply-To: <20260604094036.3777747-1-vulab@iscas.ac.cn>

On Thu, Jun 04, 2026 at 09:40:36AM +0000, Wentao Liang wrote:
> After a successful pm_runtime_get_sync(), ti_eqep_probe() can fail
> if devm_clk_get_enabled() returns an error.  In that case the
> runtime PM reference is never released, causing a refcount leak.
> 
> Fix this by adding pm_runtime_put_sync() and pm_runtime_disable()
> calls before returning the error in the clock enable failure path.
> 
> The same cleanup pattern is already used when counter_add() fails,
> so this change makes the error handling consistent.
> 
> Cc: stable@vger.kernel.org
> Fixes: 0cf81c73e4c6 ("counter: ti-eqep: enable clock at probe")
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
>  drivers/counter/ti-eqep.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/counter/ti-eqep.c b/drivers/counter/ti-eqep.c
> index d21c157e531a..84fbf500b0f8 100644
> --- a/drivers/counter/ti-eqep.c
> +++ b/drivers/counter/ti-eqep.c
> @@ -548,8 +548,11 @@ static int ti_eqep_probe(struct platform_device *pdev)
>  	pm_runtime_get_sync(dev);
> 
>  	clk = devm_clk_get_enabled(dev, NULL);
> -	if (IS_ERR(clk))
> +	if (IS_ERR(clk)) {
> +		pm_runtime_put_sync(dev);
> +		pm_runtime_disable(dev);
>  		return dev_err_probe(dev, PTR_ERR(clk), "failed to enable clock\n");
> +	}
> 
>  	err = counter_add(counter);
>  	if (err < 0) {
> --
> 2.34.1
> 

Hello Wentao,

This seems similar to another patch we're working on.[^1] I recommend
reviewing and commenting on that thread so we can consolidate there.

Thanks,

William Breathitt Gray

[^1]: https://lore.kernel.org/all/20260529095834.2561-1-sozdayvek@gmail.com/

      reply	other threads:[~2026-08-17 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04  9:40 Wentao Liang
2026-08-17 18:15 ` William Breathitt Gray [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=20260817181545.190769-1-wbg@kernel.org \
    --to=wbg@kernel.org \
    --cc=david@lechnology.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.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 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®