From: Frank Rowand <frowand.list@gmail.com>
To: "Ankit 16. Kumar (Nokia)" <ankit.16.kumar@nokia.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: overlay: fix warning being reported as error in add_changeset_property
Date: Tue, 10 Jan 2023 12:00:42 -0600 [thread overview]
Message-ID: <1194985a-1353-2f7b-3a83-eeb317dfab83@gmail.com> (raw)
In-Reply-To: <2ec3f5dc-b974-e799-2b96-d7b09dee4df1@gmail.com>
On 1/10/23 00:23, Frank Rowand wrote:
> On 1/2/23 08:35, Frank Rowand wrote:
>> On 12/30/22 02:40, Ankit 16. Kumar (Nokia) wrote:
>>>
>>> The print causes false reporting of the issue which actually is a warning
>>
>> How did you select the commit in this Fixes tag?
>>
>>> Fixes: 2fe0e8769df9 ("of: overlay: check prevents multiple fragments touching same property")
>>>
>>> Signed-off-by: Ankit Kumar <ankit.16.kumar@nokia.com>
>>> ---
>>> drivers/of/overlay.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c index ed4e6c144a68..0da39b8461e7 100644
>>> --- a/drivers/of/overlay.c
>>> +++ b/drivers/of/overlay.c
>>> @@ -358,7 +358,7 @@ static int add_changeset_property(struct overlay_changeset *ovcs,
>>> }
>>>
>>> if (!of_node_check_flag(target->np, OF_OVERLAY))
>>> - pr_err("WARNING: memory leak will occur if overlay removed, property: %pOF/%s\n",
>>> + pr_warn("WARNING: memory leak will occur if overlay removed,
>>> +property: %pOF/%s\n",
>>> target->np, new_prop->name);
>>>
>>> if (ret) {
>>> --
>>> 2.30.1
>>>
>>
>> NACK. This patch is incorrect. The reported memory leak is a bug, not a warning.
>>
>> I'll write up some information about why the memory leak occurs, then reply to this
>> email with the additional info.
>
> The additional information is now available at:
>
> https://elinux.org/Device_Tree_Linux#Object_Lifetime
I have now expanded the information at that link to content that is beyond
the original topic. Those interested in devicetree memory object may find
the additional info useful.
>
>>
>> -Frank
>
prev parent reply other threads:[~2023-01-10 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1671195782-23078-1-git-send-email-ankit.16.kumar@nokia.com>
2022-12-30 8:40 ` [PATCH] of: overlay: fix warning being reported as error in add_changeset_property Ankit 16. Kumar (Nokia)
2023-01-02 14:35 ` Frank Rowand
2023-01-10 6:23 ` Frank Rowand
2023-01-10 18:00 ` Frank Rowand [this message]
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=1194985a-1353-2f7b-3a83-eeb317dfab83@gmail.com \
--to=frowand.list@gmail.com \
--cc=ankit.16.kumar@nokia.com \
--cc=devicetree@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).