From: "Luck, Tony" <tony.luck@intel.com>
To: Kaushlendra Kumar <kaushlendra.kumar@intel.com>
Cc: <rafael@kernel.org>, <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2] ACPI: mrrm: Fix memory leaks and improve error handling
Date: Wed, 29 Oct 2025 08:23:15 -0700 [thread overview]
Message-ID: <aQIxYyNx65UQYTh3@agluck-desk3> (raw)
In-Reply-To: <20251029091013.3682552-1-kaushlendra.kumar@intel.com>
On Wed, Oct 29, 2025 at 02:40:13PM +0530, Kaushlendra Kumar wrote:
> Add proper error handling and resource cleanup to prevent memory leaks
> in add_boot_memory_ranges(). The function now checks for NULL return
> from kobject_create_and_add(), uses local buffer for range names to
> avoid dynamic allocation, and implements a cleanup path that removes
> previously created sysfs groups and kobjects on failure.
>
> This prevents resource leaks when kobject creation or sysfs group
> creation fails during boot memory range initialization.
>
> Signed-off-by: Kaushlendra Kumar <kaushlendra.kumar@intel.com>
> ---
> Changes in v2:
> - Use local buffer for range names instead of kasprintf/kfree as
> suggested in review.
>
> drivers/acpi/acpi_mrrm.c | 42 ++++++++++++++++++++++++++++++----------
> 1 file changed, 32 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/acpi/acpi_mrrm.c b/drivers/acpi/acpi_mrrm.c
> index 47ea3ccc2142..1718a35a5f56 100644
> --- a/drivers/acpi/acpi_mrrm.c
> +++ b/drivers/acpi/acpi_mrrm.c
> @@ -149,26 +149,48 @@ ATTRIBUTE_GROUPS(memory_range);
>
> static __init int add_boot_memory_ranges(void)
> {
> - struct kobject *pkobj, *kobj;
> + struct kobject *pkobj, *kobj, **kobjs;
> int ret = -EINVAL;
> - char *name;
> + char name[16];
> + int i;
>
> pkobj = kobject_create_and_add("memory_ranges", acpi_kobj);
> + if (!pkobj)
> + return -ENOMEM;
>
> - for (int i = 0; i < mrrm_mem_entry_num; i++) {
> - name = kasprintf(GFP_KERNEL, "range%d", i);
> - if (!name) {
> - ret = -ENOMEM;
> - break;
> - }
> + kobjs = kcalloc(mrrm_mem_entry_num, sizeof(*kobjs), GFP_KERNEL);
> + if (!kobjs) {
> + kobject_put(pkobj);
> + return -ENOMEM;
> + }
>
> + for (i = 0; i < mrrm_mem_entry_num; i++) {
> + snprintf(name, sizeof(name), "range%d", i);
> kobj = kobject_create_and_add(name, pkobj);
> + if (!kobj) {
> + ret = -ENOMEM;
> + goto cleanup;
> + }
>
> ret = sysfs_create_groups(kobj, memory_range_groups);
> - if (ret)
> - return ret;
> + if (ret) {
> + kobject_put(kobj);
> + goto cleanup;
> + }
> + kobjs[i] = kobj;
> }
>
Need to
kfree(kobjs);
here.
> + return 0;
> +
> +cleanup:
> + for (int j = 0; j < i; j++) {
> + if (kobjs[j]) {
> + sysfs_remove_groups(kobjs[j], memory_range_groups);
> + kobject_put(kobjs[j]);
> + }
> + }
> + kfree(kobjs);
> + kobject_put(pkobj);
> return ret;
> }
>
> --
> 2.34.1
-Tony
next prev parent reply other threads:[~2025-10-29 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 9:10 [PATCH v2] ACPI: mrrm: Fix memory leaks and improve error handling Kaushlendra Kumar
2025-10-29 15:23 ` Luck, Tony [this message]
2025-10-29 15:42 ` Kumar, Kaushlendra
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=aQIxYyNx65UQYTh3@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=kaushlendra.kumar@intel.com \
--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