From: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: alawang <alan.1.wang-FTnzSCDXTkYjo0HpFSRKWA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] of: dynamic: fix memory leak related to properties of __of_node_dup
Date: Tue, 17 Oct 2017 09:03:44 -0500 [thread overview]
Message-ID: <CAL_JsqLaOYL64SatOv-xvq0AqXTKm1BUtienFfx_qwZ8TiN+xw@mail.gmail.com> (raw)
In-Reply-To: <59E1615F.50901-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Fri, Oct 13, 2017 at 7:59 PM, Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On 10/13/17 13:47, Rob Herring wrote:
>> On Thu, Oct 12, 2017 at 8:42 PM, alawang <alan.1.wang-FTnzSCDXTkYjo0HpFSRKWA@public.gmane.org> wrote:
>>> It is possible a node was dynamically allocated but without any
>>> property. The properies will be got from devices and added to the
>>> node when devices got connected.
>>> When release this node, all properties of which had been moved to
>>> deadprops.
>>> In this case, the properties in the deadprops list are never
>>> deallocated.
>>
>> This is not new, right? Do you actually hit this case? If so, how?
>>
>>>
>>> Signed-off-by: alawang <alan.1.wang-FTnzSCDXTkYjo0HpFSRKWA@public.gmane.org>
>>> ---
>>> drivers/of/dynamic.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/of/dynamic.c b/drivers/of/dynamic.c
>>> index 301b6db..465d43b 100644
>>> --- a/drivers/of/dynamic.c
>>> +++ b/drivers/of/dynamic.c
>>> @@ -335,6 +335,10 @@ void of_node_release(struct kobject *kobj)
>>> if (!of_node_check_flag(node, OF_DYNAMIC))
>>> return;
>>>
>>> + if (!prop) {
>>> + prop = node->deadprops;
>>> + node->deadprops = NULL;
>>> + }
>>> while (prop) {
>>> struct property *next = prop->next;
>>> kfree(prop->name);
>>> --
>>> 2.6.2
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe devicetree" in
>>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> The code looks right to me. The patch description is confusing to me.
>
> 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.
What if you add 2 properties and then remove only 1. This would leave
both properties and deadprops !NULL. I think the while loop needs to
be a separate function so we iterate over both lists.
Rob
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-17 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 1:42 [PATCH] of: dynamic: fix memory leak related to properties of __of_node_dup alawang
[not found] ` <1507858967-40416-1-git-send-email-alan.1.wang-FTnzSCDXTkYjo0HpFSRKWA@public.gmane.org>
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)
[not found] ` <59E1615F.50901-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-17 14:03 ` Rob Herring [this message]
2017-10-20 1:59 ` [PATCH v4] " Lixin Wang
[not found] ` <1508464749-54218-1-git-send-email-alan.1.wang-FTnzSCDXTkYjo0HpFSRKWA@public.gmane.org>
2017-10-20 18:12 ` Rob Herring
2017-10-17 4:20 ` [PATCH v2] " Lixin Wang
2017-10-19 9:40 ` [PATCH v3] " Lixin Wang
2017-10-19 23:26 ` Frank Rowand
[not found] ` <59E934A1.9060304-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-10-19 23:34 ` frowand.list-Re5JQEeQqe8AvxtiuMwx3w
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=CAL_JsqLaOYL64SatOv-xvq0AqXTKm1BUtienFfx_qwZ8TiN+xw@mail.gmail.com \
--to=robh+dt-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=alan.1.wang-FTnzSCDXTkYjo0HpFSRKWA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).