From: Lizhi Hou <lizhi.hou@amd.com>
To: <robh@kernel.org>, <lpieralisi@kernel.org>
Cc: Lizhi Hou <lizhi.hou@amd.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH V1] of: dynamic: Fix memleak when of_pci_add_properties failed
Date: Wed, 13 Aug 2025 11:28:49 -0700 [thread overview]
Message-ID: <20250813182849.3229140-1-lizhi.hou@amd.com> (raw)
When of_pci_add_properties failed, of_changeset_destroy is called to free
the changeset. And of_changeset_destroy puts device tree node in each entry
but does not free property in the entry. This leads to memory leak in the
failure case.
In of_changeset_add_prop_helper, add the property to the device tree node
deadprops list. Thus, the property will also be freed along with device
tree node.
Fixes: b544fc2b8606 ("of: dynamic: Add interfaces for creating device node dynamically")
Reported-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
Closes: https://lore.kernel.org/all/aJms+YT8TnpzpCY8@lpieralisi/
Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
---
drivers/of/dynamic.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/of/dynamic.c b/drivers/of/dynamic.c
index 0aba760f7577..dd30b7d8b5e4 100644
--- a/drivers/of/dynamic.c
+++ b/drivers/of/dynamic.c
@@ -938,6 +938,9 @@ static int of_changeset_add_prop_helper(struct of_changeset *ocs,
if (ret)
__of_prop_free(new_pp);
+ new_pp->next = np->deadprops;
+ np->deadprops = new_pp;
+
return ret;
}
--
2.34.1
next reply other threads:[~2025-08-13 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 18:28 Lizhi Hou [this message]
2025-08-18 8:57 ` [PATCH V1] of: dynamic: Fix memleak when of_pci_add_properties failed Lorenzo Pieralisi
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=20250813182849.3229140-1-lizhi.hou@amd.com \
--to=lizhi.hou@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).