From: Andreas Kemnade <andreas@kemnade.info>
To: Haotian Zhang <vulab@iscas.ac.cn>
Cc: Kevin Hilman <khilman@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-omap@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] omap-cpufreq: Fix regulator resource leak in probe()
Date: Mon, 5 Jan 2026 10:14:12 +0100 [thread overview]
Message-ID: <20260105101412.0ac7baa7@kemnade.info> (raw)
In-Reply-To: <20251215030327.1771-1-vulab@iscas.ac.cn>
On Mon, 15 Dec 2025 11:03:27 +0800
Haotian Zhang <vulab@iscas.ac.cn> wrote:
> The current omap_cpufreq_probe() uses regulator_get() to obtain the MPU
> regulator but does not release it in omap_cpufreq_remove() or when
> cpufreq_register_driver() fails, leading to a potential resource leak.
>
> Use devm_regulator_get() instead of regulator_get() so that the regulator
> resource is automatically released.
>
> Fixes: 53dfe8a884e6 ("cpufreq: OMAP: scale voltage along with frequency")
> Signed-off-by: Haotian Zhang <vulab@iscas.ac.cn>
> ---
> drivers/cpufreq/omap-cpufreq.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/omap-cpufreq.c b/drivers/cpufreq/omap-cpufreq.c
> index bbb01d93b54b..f83f85996b36 100644
> --- a/drivers/cpufreq/omap-cpufreq.c
> +++ b/drivers/cpufreq/omap-cpufreq.c
> @@ -157,7 +157,7 @@ static int omap_cpufreq_probe(struct platform_device *pdev)
> return -EINVAL;
> }
>
> - mpu_reg = regulator_get(mpu_dev, "vcc");
> + mpu_reg = devm_regulator_get(mpu_dev, "vcc");
> if (IS_ERR(mpu_reg)) {
> pr_warn("%s: unable to get MPU regulator\n", __func__);
> mpu_reg = NULL;
> @@ -169,7 +169,6 @@ static int omap_cpufreq_probe(struct platform_device *pdev)
> if (regulator_get_voltage(mpu_reg) < 0) {
> pr_warn("%s: physical regulator not present for MPU\n",
> __func__);
> - regulator_put(mpu_reg);
so it it not useable and could be released which is not done anymare
with your patch. It is not an error path here.
> mpu_reg = NULL;
And this should happen after removal, too. I feel some discomfort with
variables pointing to freed ressources. So I think rather add
the regulator_put and the = NULL to the remove function.
Regards,
Andreas
next prev parent reply other threads:[~2026-01-05 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 3:03 [PATCH] omap-cpufreq: Fix regulator resource leak in probe() Haotian Zhang
2026-01-05 5:16 ` Viresh Kumar
2026-01-05 9:14 ` Andreas Kemnade [this message]
2026-01-06 4:50 ` Viresh Kumar
2026-01-06 17:29 ` Andreas Kemnade
2026-01-07 5:57 ` Viresh Kumar
2026-01-07 7:58 ` Andreas Kemnade
2026-01-05 13:12 ` [PATCH v2] cpufreq: OMAP: Fix resource leak in probe error path and remove Haotian Zhang
2026-01-06 4:51 ` Viresh Kumar
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=20260105101412.0ac7baa7@kemnade.info \
--to=andreas@kemnade.info \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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