From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
djrscally@gmail.com, heikki.krogerus@linux.intel.com,
sakari.ailus@linux.intel.com, gregkh@linuxfoundation.org,
rafael@kernel.org
Subject: Re: [PATCH v2] device property: fix of node refcount leak in fwnode_graph_get_next_endpoint()
Date: Tue, 22 Nov 2022 16:22:35 +0200 [thread overview]
Message-ID: <Y3zbK4ngD8xZBqsf@smile.fi.intel.com> (raw)
In-Reply-To: <Y3zXjpY2/Le/3J9q@smile.fi.intel.com>
On Tue, Nov 22, 2022 at 04:07:10PM +0200, Andy Shevchenko wrote:
> On Tue, Nov 22, 2022 at 09:41:28PM +0800, Yang Yingliang wrote:
> > On 2022/11/22 21:16, Andy Shevchenko wrote:
> > > On Tue, Nov 22, 2022 at 09:12:41PM +0800, Yang Yingliang wrote:
> > > > On 2022/11/22 20:54, Andy Shevchenko wrote:
> > > > > On Tue, Nov 22, 2022 at 08:00:39PM +0800, Yang Yingliang wrote:
...
> > > > > It seems too complicated for the simple fix.
> > > > >
> > > > > As I said, just drop const qualifier and add fwnode_handle_get() in the 'else'
> > > > > branch. This will allow you to drop if (prev) at the end.
> > > > fwnode is const, fwnode_handle_get doesn't accept this type.
> > > I'm talking about parent.
> > You suggested this:
> >
> > "Instead you might consider to replace
> >
> > parent = fwnode;
> >
> > by
> >
> > parent = fwnode_handle_get(fwnode);"
> >
> >
> > It has compile warning:
> > drivers/base/property.c: In function ‘fwnode_graph_get_next_endpoint’:
> > drivers/base/property.c:1004:30: warning: passing argument 1 of ‘fwnode_handle_get’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
> > parent = fwnode_handle_get(fwnode);
> > ^~~~~~
> > drivers/base/property.c:809:63: note: expected ‘struct fwnode_handle *’ but argument is of type ‘const struct fwnode_handle *’
> > struct fwnode_handle *fwnode_handle_get(struct fwnode_handle *fwnode)
> >
> > ~~~~~~~~~~~~~~~~~~~~~~^~~~~~
>
> I see what you mean. Thank you for clarification.
>
> So, it seems a bit twisted.
>
> If prev == NULL, can the
>
> ep = fwnode_call_ptr_op(parent, graph_get_next_endpoint, NULL);
>
> return NULL?
>
> If no, we may move this case directly to the 'else' branch and return from there.
Answering to my own question: unfortunately it's the case when we have no
endpoints for the fwnode, but might have for the secondary one.
Okay, let's proceed with your slightly modified version 2 (label) for now.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-22 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:00 [PATCH v2] device property: fix of node refcount leak in fwnode_graph_get_next_endpoint() Yang Yingliang
2022-11-22 12:54 ` Andy Shevchenko
2022-11-22 12:56 ` Andy Shevchenko
2022-11-22 12:58 ` Andy Shevchenko
2022-11-22 13:14 ` Yang Yingliang
2022-11-22 13:12 ` Yang Yingliang
2022-11-22 13:16 ` Andy Shevchenko
2022-11-22 13:41 ` Yang Yingliang
2022-11-22 14:07 ` Andy Shevchenko
2022-11-22 14:22 ` Andy Shevchenko [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=Y3zbK4ngD8xZBqsf@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.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