From: Lixin Wang <alan.1.wang@nokia-sbell.com>
To: Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Lixin Wang <alan.1.wang@nokia-sbell.com>
Subject: [PATCH v3] of: dynamic: fix memory leak related to properties of __of_node_dup
Date: Thu, 19 Oct 2017 17:40:06 +0800 [thread overview]
Message-ID: <1508406006-64893-1-git-send-email-alan.1.wang@nokia-sbell.com> (raw)
In-Reply-To: <1507858967-40416-1-git-send-email-alan.1.wang@nokia-sbell.com>
If a node with no properties is dynamically added, then a property is
dynamically added to the node, then the property is dynamically removed,
the result will be node->properties == NULL and node->deadprops != NULL.
Add a separate function to release the properties in both lists.
Signed-off-by: Lixin Wang <alan.1.wang@nokia-sbell.com>
---
v2 -> v3:
* Add a separate function to release the properties in both lists.
* Change the patch description for this change.
drivers/of/dynamic.c | 27 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/drivers/of/dynamic.c b/drivers/of/dynamic.c
index 301b6db..b28511f 100644
--- a/drivers/of/dynamic.c
+++ b/drivers/of/dynamic.c
@@ -315,6 +315,19 @@ int of_detach_node(struct device_node *np)
}
EXPORT_SYMBOL_GPL(of_detach_node);
+static void __of_property_list_release(struct property *prop)
+{
+ struct property *next;
+
+ while (prop) {
+ next = prop->next;
+ kfree(prop->name);
+ kfree(prop->value);
+ kfree(prop);
+ prop = next;
+ }
+}
+
/**
* of_node_release() - release a dynamically allocated node
* @kref: kref element of the node to be released
@@ -324,7 +337,6 @@ EXPORT_SYMBOL_GPL(of_detach_node);
void of_node_release(struct kobject *kobj)
{
struct device_node *node = kobj_to_device_node(kobj);
- struct property *prop = node->properties;
/* We should never be releasing nodes that haven't been detached. */
if (!of_node_check_flag(node, OF_DETACHED)) {
@@ -335,18 +347,9 @@ void of_node_release(struct kobject *kobj)
if (!of_node_check_flag(node, OF_DYNAMIC))
return;
- while (prop) {
- struct property *next = prop->next;
- kfree(prop->name);
- kfree(prop->value);
- kfree(prop);
- prop = next;
+ __of_property_list_release(node->properties);
+ __of_property_list_release(node->deadprops);
- if (!prop) {
- prop = node->deadprops;
- node->deadprops = NULL;
- }
- }
kfree(node->full_name);
kfree(node->data);
kfree(node);
--
2.6.2
next prev parent reply other threads:[~2017-10-19 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 1:42 [PATCH] " alawang
2017-10-13 3:25 ` Lixin Wang
2017-10-13 20:47 ` Rob Herring
2017-10-14 0:59 ` Frank Rowand
2017-10-16 4:35 ` Wang, Alan 1. (NSB - CN/Hangzhou)
2017-10-17 14:03 ` Rob Herring
2017-10-17 4:20 ` [PATCH v2] " Lixin Wang
2017-10-19 9:40 ` Lixin Wang [this message]
2017-10-19 23:26 ` [PATCH v3] " Frank Rowand
2017-10-19 23:34 ` frowand.list
2017-10-20 1:59 ` [PATCH v4] " Lixin Wang
2017-10-20 18:12 ` Rob Herring
2017-10-23 3:19 ` [PATCH v5] " Lixin Wang
2017-10-23 5:16 ` Frank Rowand
2017-10-23 16:47 ` Rob Herring
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=1508406006-64893-1-git-send-email-alan.1.wang@nokia-sbell.com \
--to=alan.1.wang@nokia-sbell.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®