From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Bartosz Golaszewski <brgl@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Johan Hovold <johan@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org,
Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
Subject: Re: [PATCH] software node: only let the owner release a managed node
Date: Fri, 6 Nov 2026 18:47:18 +0100 [thread overview]
Message-ID: <au4Spi8lWIs4C0ca@black.igk.intel.com> (raw)
In-Reply-To: <20261102-swnode-only-owner-release-v1-1-ee4c9022a629@oss.qualcomm.com>
On Mon, Nov 02, 2026 at 04:25:16PM +0100, Bartosz Golaszewski wrote:
> device_create_managed_software_node() creates a node whose lifetime is
> tied to the device it was created for. software_node_notify_remove() is
> called for every device that has the node as its fwnode (primary OR
> secondary) and, if the node is managed, unconditionally detaches it from
> that device and drops the creation reference.
>
> This breaks when the node is shared with another device. Example: the
> i2c-designware copies the parent's fwnode to the adapter's struct device.
> When the adapter is deleted, it releases the reference that belongs to
> the owner and the latter ends up with a dangling pointer.
>
> Record the device's "manager" and only perform the actual release when
> notify is called for that "owner" device.
>
> Reported-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> Closes: https://lore.kernel.org/all/20261009164241.923756-2-balasubramani.vivekanandan@intel.com/
> Fixes: 151f6ff78cdf ("software node: Provide replacement for device_add_properties()")
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
LGTM. FWIW:
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> Hi!
>
> This is my approach at addressing the bug reported by Vivekanandan
> directly in driver core. Please test it if you can.
>
> Thanks,
> Bartosz
> ---
> drivers/base/swnode.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/swnode.c b/drivers/base/swnode.c
> index 84a77ffa3dc4bbcca62bbe67c3390693500b01ea..abb6d6d59d59cb4e605fc31cc7e89f92e9f900a6 100644
> --- a/drivers/base/swnode.c
> +++ b/drivers/base/swnode.c
> @@ -29,6 +29,8 @@ struct swnode {
> struct fwnode_handle fwnode;
> const struct software_node *node;
> int id;
> + /* Device the managed node's lifetime is tied to. */
> + struct device *owner;
>
> /* hierarchy */
> struct ida child_ids;
> @@ -37,7 +39,6 @@ struct swnode {
> struct swnode *parent;
>
> unsigned int allocated:1;
> - unsigned int managed:1;
> };
>
> static DEFINE_IDA(swnode_root_ids);
> @@ -1145,7 +1146,7 @@ int device_create_managed_software_node(struct device *dev,
> if (IS_ERR(fwnode))
> return PTR_ERR(fwnode);
>
> - to_swnode(fwnode)->managed = true;
> + to_swnode(fwnode)->owner = dev;
> set_secondary_fwnode(dev, fwnode);
>
> if (device_is_registered(dev))
> @@ -1190,6 +1191,7 @@ void software_node_notify(struct device *dev)
> void software_node_notify_remove(struct device *dev)
> {
> struct swnode *swnode;
> + bool is_owner;
>
> swnode = dev_to_swnode(dev);
> if (!swnode)
> @@ -1206,9 +1208,13 @@ void software_node_notify_remove(struct device *dev)
> if (!device_match_fwnode(dev, &swnode->fwnode) && swnode->fwnode.dev == dev)
> swnode->fwnode.dev = NULL;
>
> + is_owner = swnode->owner && swnode->owner == dev;
> + if (is_owner)
> + swnode->owner = NULL;
> +
> swnode_put(swnode);
>
> - if (swnode->managed) {
> + if (is_owner) {
> set_secondary_fwnode(dev, NULL);
> swnode_put(swnode);
> }
>
> ---
> base-commit: 7649ba73f9e7e1e04d0b46213e39c79ae09dd55c
> change-id: 20261102-swnode-only-owner-release-45efdc7123e1
>
> Best regards,
> --
> Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
--
heikki
next prev parent reply other threads:[~2026-11-06 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 15:25 [PATCH] software node: only let the owner release a managed node Bartosz Golaszewski
2026-11-04 6:47 ` Vivekanandan, Balasubramani
2026-11-04 8:19 ` Andy Shevchenko
2026-11-04 8:26 ` Vivekanandan, Balasubramani
2026-11-04 8:35 ` Andy Shevchenko
2026-11-04 8:40 ` Vivekanandan, Balasubramani
2026-11-06 17:47 ` Heikki Krogerus [this message]
2026-11-09 13:37 ` Johan Hovold
2026-11-09 14:10 ` Danilo Krummrich
2026-11-09 14:30 ` Bartosz Golaszewski
2026-11-09 14:34 ` Johan Hovold
2026-11-09 14:45 ` Danilo Krummrich
2026-11-09 14:59 ` Johan Hovold
2026-11-09 15:17 ` Danilo Krummrich
2026-11-09 15:55 ` Johan Hovold
2026-11-09 16:08 ` Bartosz Golaszewski
2026-11-09 16:20 ` Johan Hovold
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=au4Spi8lWIs4C0ca@black.igk.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.