From: Frank Rowand <frowand.list@gmail.com>
To: Yang Yingliang <yangyingliang@huawei.com>, devicetree@vger.kernel.org
Cc: sakari.ailus@linux.intel.com, rafael.j.wysocki@intel.com,
robh+dt@kernel.org
Subject: Re: [PATCH v2] of: property: decrement node refcount in of_fwnode_get_reference_args()
Date: Sun, 20 Nov 2022 20:06:05 -0600 [thread overview]
Message-ID: <412db8f1-eea5-4029-e1d0-0cc73b5be80a@gmail.com> (raw)
In-Reply-To: <20221121014200.3560742-1-yangyingliang@huawei.com>
On 11/20/22 19:42, Yang Yingliang wrote:
Thanks for the quick update to v2.
This part of the patch comment should also be removed, because (if I understand
correctly) it does not occur in the existing tree, only if a proposed patch is
applied:
> I got the the following report:
>
> OF: ERROR: memory leak, expected refcount 1 instead of 4,
> of_node_get()/of_node_put() unbalanced - destroy cset entry:
> attach overlay node /i2c/pmic@34/adc
Am I correct? In any case I appreciate the error report which
provides useful context for the underlying problem.
-Frank
>
> In of_fwnode_get_reference_args(), the refcount of of_args.np has
> been incremented in the case of successful return from
> of_parse_phandle_with_args() or of_parse_phandle_with_fixed_args().
>
> Decrement the refcount if of_args is not returned to the caller of
> of_fwnode_get_reference_args().
>
> Fixes: 3e3119d3088f ("device property: Introduce fwnode_property_get_reference_args")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Reviewed-by: Frank Rowand <frowand.list@gmail.com>
> ---
> v1 -> v2:
> Update title and commit message that suggested by Frank.
> ---
> drivers/of/property.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/of/property.c b/drivers/of/property.c
> index 967f79b59016..134cfc980b70 100644
> --- a/drivers/of/property.c
> +++ b/drivers/of/property.c
> @@ -993,8 +993,10 @@ of_fwnode_get_reference_args(const struct fwnode_handle *fwnode,
> nargs, index, &of_args);
> if (ret < 0)
> return ret;
> - if (!args)
> + if (!args) {
> + of_node_put(of_args.np);
> return 0;
> + }
>
> args->nargs = of_args.args_count;
> args->fwnode = of_fwnode_handle(of_args.np);
prev parent reply other threads:[~2022-11-21 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 1:42 [PATCH v2] of: property: decrement node refcount in of_fwnode_get_reference_args() Yang Yingliang
2022-11-21 2:06 ` 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=412db8f1-eea5-4029-e1d0-0cc73b5be80a@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=yangyingliang@huawei.com \
/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).