From: Changwoo Min <changwoo@igalia.com>
To: Malaya Kumar Rout <mrout@redhat.com>, linux-kernel@vger.kernel.org
Cc: malayarout91@gmail.com, Lukasz Luba <lukasz.luba@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@kernel.org>, Len Brown <lenb@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] PM: EM: Fix memory leak in em_create_pd() error path
Date: Thu, 8 Jan 2026 14:44:38 +0900 [thread overview]
Message-ID: <28e46f37-54be-4c28-a7a8-2b3e80a8cd30@igalia.com> (raw)
In-Reply-To: <20260105103730.65626-1-mrout@redhat.com>
Thanks, Malaya, for the bug fix. This makes sense to me.
Reviewed-by: Changwoo Min <changwoo@igalia.com>
On 1/5/26 7:37 PM, Malaya Kumar Rout wrote:
> When ida_alloc() fails in em_create_pd(), the function returns without
> freeing the previously allocated 'pd' structure, leading to a memory leak.
> The 'pd' pointer is allocated either at line 436 (for CPU devices with
> cpumask) or line 442 (for other devices) using kzalloc().
>
> Additionally, the function incorrectly returns -ENOMEM when ida_alloc()
> fails, ignoring the actual error code returned by ida_alloc(), which can
> fail for reasons other than memory exhaustion.
>
> Fix both issues by:
> 1. Freeing the 'pd' structure with kfree() when ida_alloc() fails
> 2. Returning the actual error code from ida_alloc() instead of -ENOMEM
>
> This ensures proper cleanup on the error path and accurate error reporting.
>
> Fixes: cbe5aeedecc7 ("PM: EM: Assign a unique ID when creating a performance domain")
> Signed-off-by: Malaya Kumar Rout <mrout@redhat.com>
> ---
> kernel/power/energy_model.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/power/energy_model.c b/kernel/power/energy_model.c
> index 11af9f64aa82..5b055cbe5341 100644
> --- a/kernel/power/energy_model.c
> +++ b/kernel/power/energy_model.c
> @@ -449,8 +449,10 @@ static int em_create_pd(struct device *dev, int nr_states,
> INIT_LIST_HEAD(&pd->node);
>
> id = ida_alloc(&em_pd_ida, GFP_KERNEL);
> - if (id < 0)
> - return -ENOMEM;
> + if (id < 0) {
> + kfree(pd);
> + return id;
> + }
> pd->id = id;
>
> em_table = em_table_alloc(pd);
next prev parent reply other threads:[~2026-01-08 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 10:37 Malaya Kumar Rout
2026-01-08 5:44 ` Changwoo Min [this message]
2026-01-08 15:56 ` Rafael J. Wysocki
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=28e46f37-54be-4c28-a7a8-2b3e80a8cd30@igalia.com \
--to=changwoo@igalia.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=malayarout91@gmail.com \
--cc=mrout@redhat.com \
--cc=pavel@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®