mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wentao Liang <vulab@iscas.ac.cn>
To: Li.Xiubo@freescale.com
Cc: daniel.lezcano@kernel.org, linux-kernel@vger.kernel.org,
	tglx@kernel.org, lkml@vger.kernel.org,
	Wentao Liang <vulab@iscas.ac.cn>,
	stable@vger.kernel.org
Subject: [PATCH] clocksource/drivers/timer-fsl-ftm: Fix clk reference leak in error paths
Date: Tue, 15 Sep 2026 05:02:58 +0000	[thread overview]
Message-ID: <20260915050258.1727196-1-vulab@iscas.ac.cn> (raw)

__ftm_clk_init() obtains clock references with of_clk_get_by_name() but
never releases them on the error paths. If clk_prepare_enable() fails on
the counter clock, the reference is leaked. The second of_clk_get_by_name()
also overwrites the first clk pointer, so a failure to get or prepare the
ftm clock loses the counter clock reference as well; on the get failure
path the counter clock is left enabled and unreferenced.

Release the references on the error paths: clk_put() when prepare+enable
fails, and clk_disable_unprepare() followed by clk_put() when aborting
after the counter clock has been enabled. The clocks intentionally stay
enabled on the success path, so those are left untouched.

Fixes: 2529c3a33079 ("clocksource: Add Freescale FlexTimer Module (FTM) timer support")
Cc: stable@vger.kernel.org
Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
---
 drivers/clocksource/timer-fsl-ftm.c | 25 +++++++++++++++++--------
 1 file changed, 17 insertions(+), 8 deletions(-)

diff --git a/drivers/clocksource/timer-fsl-ftm.c b/drivers/clocksource/timer-fsl-ftm.c
index 4eed6cb46132..8ada0c3e088a 100644
--- a/drivers/clocksource/timer-fsl-ftm.c
+++ b/drivers/clocksource/timer-fsl-ftm.c
@@ -230,7 +230,8 @@ static int __init ftm_clocksource_init(unsigned long freq)
 static int __init __ftm_clk_init(struct device_node *np, char *cnt_name,
 				 char *ftm_name)
 {
-	struct clk *clk;
+	struct clk *clk, *ftm_clk;
+	unsigned long rate;
 	int err;
 
 	clk = of_clk_get_by_name(np, cnt_name);
@@ -242,20 +243,28 @@ static int __init __ftm_clk_init(struct device_node *np, char *cnt_name,
 	if (err) {
 		pr_err("ftm: clock failed to prepare+enable \"%s\": %d\n",
 			cnt_name, err);
+		clk_put(clk);
 		return err;
 	}
 
-	clk = of_clk_get_by_name(np, ftm_name);
-	if (IS_ERR(clk)) {
-		pr_err("ftm: Cannot get \"%s\": %ld\n", ftm_name, PTR_ERR(clk));
-		return PTR_ERR(clk);
+	ftm_clk = of_clk_get_by_name(np, ftm_name);
+	if (IS_ERR(ftm_clk)) {
+		pr_err("ftm: Cannot get \"%s\": %ld\n", ftm_name,
+			PTR_ERR(ftm_clk));
+		clk_disable_unprepare(clk);
+		clk_put(clk);
+		return PTR_ERR(ftm_clk);
 	}
-	err = clk_prepare_enable(clk);
-	if (err)
+	err = clk_prepare_enable(ftm_clk);
+	if (err) {
 		pr_err("ftm: clock failed to prepare+enable \"%s\": %d\n",
 			ftm_name, err);
+		rate = clk_get_rate(ftm_clk);
+		clk_put(ftm_clk);
+		return rate;
+	}
 
-	return clk_get_rate(clk);
+	return clk_get_rate(ftm_clk);
 }
 
 static unsigned long __init ftm_clk_init(struct device_node *np)
-- 
2.34.1


             reply	other threads:[~2026-09-15  5:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  5:02 Wentao Liang [this message]
2026-09-21 15:32 ` krzk

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=20260915050258.1727196-1-vulab@iscas.ac.cn \
    --to=vulab@iscas.ac.cn \
    --cc=Li.Xiubo@freescale.com \
    --cc=daniel.lezcano@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@kernel.org \
    /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®