From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Xu Yang <xu.yang_2@oss.nxp.com>, Bartosz Golaszewski <brgl@kernel.org>
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 0/2] device property: fix child iteration issues with secondary fwnodes
Date: Wed, 3 Jun 2026 12:43:06 +0300 [thread overview]
Message-ID: <ah_3KmASlE44X4Xw@ashevche-desk.local> (raw)
In-Reply-To: <20260603-fixes_fwnode_iteration-v2-0-0ae381f8b7b9@nxp.com>
On Wed, Jun 03, 2026 at 04:44:30PM +0800, Xu Yang wrote:
> This series fixes two issues in the fwnode child iteration logic when
> a secondary fwnode is present.
>
> The first patch addresses a refcount imbalance in
> software_node_get_next_child(). When a software node is used as a
> secondary fwnode, the iteration code may incorrectly decrement the
> refcount of child nodes that do not belong to the software node
> hierarchy. This results in refcount underflow and possible use-after-free.
>
> The second patch fixes an infinite loop in
> fwnode_for_each_child_node(), caused by improper handling of iteration
> state across primary and secondary fwnodes. When iterating over children
> from both primary and secondary fwnodes, the code may incorrectly
> resume iteration from the primary fwnode even when the current child
> belongs to the secondary, leading to repeated traversal and a loop.
>
> Both issues are triggered when mixing different fwnode types through the
> secondary mechanism, and stem from incorrect assumptions about ownership
> and traversal context of child nodes.
Please, Cc Bart who is heavily working on software nodes these days.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-06-03 9:43 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
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 ` Andy Shevchenko [this message]
2026-06-04 10:58 ` [PATCH v2 0/2] device property: fix child iteration issues with secondary fwnodes 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=ah_3KmASlE44X4Xw@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--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