From: Zeng Heng <zengheng4@huawei.com>
To: Frank Rowand <frowand.list@gmail.com>,
<pantelis.antoniou@konsulko.com>, <grant.likely@linaro.org>,
<robh+dt@kernel.org>
Cc: <liwei391@huawei.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: overlay: fix memory leak in add_changeset_node()
Date: Mon, 21 Nov 2022 11:37:29 +0800 [thread overview]
Message-ID: <f0c641ee-b20d-48dd-c65f-2b372eae0b06@huawei.com> (raw)
In-Reply-To: <8c8124c1-2de6-adfd-3e4b-766c653ebe2d@gmail.com>
On 2022/11/21 10:00, Frank Rowand wrote:
> On 11/18/22 04:53, Zeng Heng wrote:
>> In of_changeset_action(), we have called of_node_get() to increase
>> refcount of a node.
>>
>> Therefore, when tchild (duplicated by __of_node_dup()) is done,
>> of_node_put() needs to call and release the device_node.
>>
>> Otherwise, there are some memory leak reported about the node:
>>
>> unreferenced object 0xffff88810cd1e800 (size 256):
>> backtrace:
>> kmalloc_trace
>> __of_node_dup
>> add_changeset_node (inlined)
>> build_changeset_next_level
>>
>> unreferenced object 0xffff888113721240 (size 16):
>> backtrace:
>> __kmalloc_node_track_caller
>> kstrdup
>> __of_node_dup
>> add_changeset_node (inlined)
>> build_changeset_next_level
>>
>> unreferenced object 0xffff88810a38d400 (size 128):
>> backtrace:
>> kmalloc_trace
>> __of_prop_dup
>> add_changeset_property
>> build_changeset_next_level
>>
>> Fixes: 7518b5890d8a ("of/overlay: Introduce DT overlay support")
>> Signed-off-by: Zeng Heng<zengheng4@huawei.com>
>> ---
>> drivers/of/overlay.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c
>> index bd8ff4df723d..a5189a0ec0a3 100644
>> --- a/drivers/of/overlay.c
>> +++ b/drivers/of/overlay.c
>> @@ -436,8 +436,10 @@ static int add_changeset_node(struct overlay_changeset *ovcs,
>> of_node_set_flag(tchild, OF_OVERLAY);
>>
>> ret = of_changeset_attach_node(&ovcs->cset, tchild);
>> - if (ret)
>> + if (ret) {
>> + of_node_put(tchild);
>> return ret;
>> + }
> By visual inspection of the code (Linux 6.1-rc1), this does not appear to be
> correct. For the only case where of_changeset_action(),
> called by of_changeset_attach_node(), returns an error, of_node_get() has not
> yet occurred on tchild.
The correct explanation should be like:
When of_changeset_attach_node() returns fail and tchild is over of life
cycle which is duplicated by
__of_node_dup(), it needs to call of_node_put() to release tchild in
error handle route.
The patch is fine, but feel sorry to apologize for the incorrect comment
of the patch.
I would update the comment in the patch v2.
With Best Regards,
Zeng Heng
>>
>> target_child.np = tchild;
>> target_child.in_livetree = false;
> For which version of Linux were the memory leaks detected? Were any additional
> patches applied?
>
> -Frank
next prev parent reply other threads:[~2022-11-21 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 10:53 [PATCH] of: overlay: fix memory leak in add_changeset_node() Zeng Heng
2022-11-21 2:00 ` Frank Rowand
2022-11-21 3:37 ` Zeng Heng [this message]
2022-11-21 3:53 ` [PATCH v2] " Zeng Heng
2022-11-21 6:07 ` Zeng Heng
2022-11-23 0:29 ` Frank Rowand
2022-11-23 1:16 ` Frank Rowand
2022-11-23 1:52 ` Zeng Heng
2022-11-23 1:41 ` Zeng Heng
2022-12-01 22:54 ` [PATCH] " Frank Rowand
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=f0c641ee-b20d-48dd-c65f-2b372eae0b06@huawei.com \
--to=zengheng4@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=pantelis.antoniou@konsulko.com \
--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