From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Xu Yang <xu.yang_2@oss.nxp.com>
Cc: Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-acpi@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org, Xu Yang <xu.yang_2@nxp.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] software node: fix refcount leak in software_node_get_next_child()
Date: Thu, 4 Jun 2026 20:50:16 +0300 [thread overview]
Message-ID: <aiG62GXa3tYhhMBQ@ashevche-desk.local> (raw)
In-Reply-To: <soxsu3t7ntgnbeeic5mygklzdpohyic7echo5trnzuphbpe6b6@avr5wwkbojvm>
On Thu, Jun 04, 2026 at 07:15:26PM +0800, Xu Yang wrote:
> On Wed, Jun 03, 2026 at 12:40:27PM +0300, Andy Shevchenko wrote:
> > On Wed, Jun 03, 2026 at 04:44:31PM +0800, Xu Yang wrote:
...
> > > struct swnode *p = to_swnode(fwnode);
> > > struct swnode *c = to_swnode(child);
> > >
> > > - if (!p || list_empty(&p->children) ||
> > > - (c && list_is_last(&c->entry, &p->children))) {
> > > - fwnode_handle_put(child);
> >
> > Wouldn't be better to use swnode_get() / swnode_put() instead?
> > *Yes, we might need to add some NULL checks there.
>
> It's not newly added by me. The software_node_get_next_child() has been using
> fwnode_handle_get() / fwnode_handle_put() before. In my opinion, this should
> be fine since they do the same thing here for a swnode.
It doesn't matter who added that. But according to the point of this patch
(correct me if I am wrong) is to avoid bumping or dropping reference count for
the nodes that are *not* of swnode type. Moving away from fwnode_handle_*()
loop we make the point clear.
See the of_get_next_status_child() implementation, it does *not* use
fwnode_handle_*() at all. So, making it here to use same approach should
fix your issue, no?
> > > + if (!p || list_empty(&p->children))
> > > return NULL;
> > > - }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-06-04 17:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 8:44 [PATCH v2 0/2] device property: fix child iteration issues with secondary fwnodes Xu Yang
2026-06-03 8:44 ` [PATCH v2 1/2] software node: fix refcount leak in software_node_get_next_child() Xu Yang
2026-06-03 9:40 ` Andy Shevchenko
2026-06-04 11:15 ` Xu Yang
2026-06-04 17:50 ` Andy Shevchenko [this message]
2026-06-05 9:16 ` Xu Yang
2026-06-05 15:20 ` Andy Shevchenko
2026-06-08 2:35 ` Xu Yang
2026-06-03 8:44 ` [PATCH v2 2/2] device property: fix infinite loop in fwnode_for_each_child_node() Xu Yang
2026-06-03 9:51 ` Andy Shevchenko
2026-06-04 11:05 ` Xu Yang
2026-06-04 13:43 ` Bartosz Golaszewski
2026-06-04 15:21 ` Xu Yang
2026-06-03 9:43 ` [PATCH v2 0/2] device property: fix child iteration issues with secondary fwnodes Andy Shevchenko
2026-06-04 10:58 ` Xu Yang
2026-06-04 13:38 ` Bartosz Golaszewski
2026-06-04 17:52 ` 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=aiG62GXa3tYhhMBQ@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=xu.yang_2@nxp.com \
--cc=xu.yang_2@oss.nxp.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