From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <daniel.lezcano@kernel.org>, <rafael@kernel.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powercap: dtpm_devfreq: Fix possible memory leak in __dtpm_devfreq_setup()
Date: Thu, 7 Nov 2024 09:30:12 +0800 [thread overview]
Message-ID: <2d04feea-c568-5ff8-019b-119b824e8a0f@huawei.com> (raw)
In-Reply-To: <20241026082525.474914-1-ruanjinjie@huawei.com>
Gentle ping.
On 2024/10/26 16:25, Jinjie Ruan wrote:
> If dev_pm_qos_add_request() fails, dtpm_devfreq will fail
> to free, which cause the memory leak, add a new goto label
> to free it.
>
> Fixes: e44655617317 ("powercap/drivers/dtpm: Add dtpm devfreq with energy model support")
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
> drivers/powercap/dtpm_devfreq.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/powercap/dtpm_devfreq.c b/drivers/powercap/dtpm_devfreq.c
> index d1dff6ccab12..85b6982901d1 100644
> --- a/drivers/powercap/dtpm_devfreq.c
> +++ b/drivers/powercap/dtpm_devfreq.c
> @@ -171,8 +171,7 @@ static int __dtpm_devfreq_setup(struct devfreq *devfreq, struct dtpm *parent)
> ret = dtpm_register(dev_name(dev), &dtpm_devfreq->dtpm, parent);
> if (ret) {
> pr_err("Failed to register '%s': %d\n", dev_name(dev), ret);
> - kfree(dtpm_devfreq);
> - return ret;
> + goto out_dtpm_free;
> }
>
> ret = dev_pm_qos_add_request(dev, &dtpm_devfreq->qos_req,
> @@ -190,6 +189,8 @@ static int __dtpm_devfreq_setup(struct devfreq *devfreq, struct dtpm *parent)
> out_dtpm_unregister:
> dtpm_unregister(&dtpm_devfreq->dtpm);
>
> +out_dtpm_free:
> + kfree(dtpm_devfreq);
> return ret;
> }
>
prev parent reply other threads:[~2024-11-07 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 8:25 Jinjie Ruan
2024-11-07 1:30 ` Jinjie Ruan [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=2d04feea-c568-5ff8-019b-119b824e8a0f@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=daniel.lezcano@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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®