From: Daniel Scally <djrscally@gmail.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com,
heikki.krogerus@linux.intel.com, sakari.ailus@linux.intel.com,
gregkh@linuxfoundation.org, rafael@kernel.org
Subject: Re: [PATCH v3] device property: fix of node refcount leak in fwnode_graph_get_next_endpoint()
Date: Fri, 25 Nov 2022 15:50:53 +0000 [thread overview]
Message-ID: <5beff345-84c2-d456-1b7f-05309afa397b@gmail.com> (raw)
In-Reply-To: <20221123022542.2999510-1-yangyingliang@huawei.com>
Hi all - sorry that took so long
On 23/11/2022 02:25, Yang Yingliang wrote:
> The 'parent' returned by fwnode_graph_get_port_parent()
> with refcount incremented when 'prev' is not NULL, it
> needs be put when finish using it.
>
> Because the parent is const, introduce a new variable to
> store the returned fwnode, then put it before returning
> from fwnode_graph_get_next_endpoint().
>
> Fixes: b5b41ab6b0c1 ("device property: Check fwnode->secondary in fwnode_graph_get_next_endpoint()")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
This looks fine to me (thanks for fixing it), and it works fine on my
Surface:
Reviewed-and-tested-by: Daniel Scally <djrscally@gmail.com>
> v2 -> v3:
> Add a out label.
>
> v1 -> v2:
> Introduce a new variable to store the returned fwnode.
> ---
> drivers/base/property.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/base/property.c b/drivers/base/property.c
> index 2a5a37fcd998..7f338cb4fb7b 100644
> --- a/drivers/base/property.c
> +++ b/drivers/base/property.c
> @@ -989,26 +989,32 @@ struct fwnode_handle *
> fwnode_graph_get_next_endpoint(const struct fwnode_handle *fwnode,
> struct fwnode_handle *prev)
> {
> + struct fwnode_handle *ep, *port_parent = NULL;
> const struct fwnode_handle *parent;
> - struct fwnode_handle *ep;
>
> /*
> * If this function is in a loop and the previous iteration returned
> * an endpoint from fwnode->secondary, then we need to use the secondary
> * as parent rather than @fwnode.
> */
> - if (prev)
> - parent = fwnode_graph_get_port_parent(prev);
> - else
> + if (prev) {
> + port_parent = fwnode_graph_get_port_parent(prev);
> + parent = port_parent;
> + } else {
> parent = fwnode;
> + }
> if (IS_ERR_OR_NULL(parent))
> return NULL;
>
> ep = fwnode_call_ptr_op(parent, graph_get_next_endpoint, prev);
> if (ep)
> - return ep;
> + goto out_put_port_parent;
> +
> + ep = fwnode_graph_get_next_endpoint(parent->secondary, NULL);
>
> - return fwnode_graph_get_next_endpoint(parent->secondary, NULL);
> +out_put_port_parent:
> + fwnode_handle_put(port_parent);
> + return ep;
> }
> EXPORT_SYMBOL_GPL(fwnode_graph_get_next_endpoint);
>
next prev parent reply other threads:[~2022-11-25 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 2:25 [PATCH v3] device property: fix of node refcount leak in fwnode_graph_get_next_endpoint() Yang Yingliang
2022-11-23 13:31 ` Andy Shevchenko
2022-11-25 9:32 ` Daniel Scally
2022-11-25 9:49 ` Yang Yingliang
2022-11-25 9:59 ` Sakari Ailus
2022-11-25 15:50 ` Daniel Scally [this message]
2022-12-28 9:37 ` Andy Shevchenko
2022-12-28 9:46 ` Greg KH
2022-12-28 9:50 ` Andy Shevchenko
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=5beff345-84c2-d456-1b7f-05309afa397b@gmail.com \
--to=djrscally@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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