| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20240123014517.5787-3-mcpratt@pm.me>
Date: Tue, 23 Jan 2024 01:46:40 +0000
From: Michael Pratt <mcpratt@...me>
To: devicetree@...r.kernel.org, gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org
Cc: Michael Pratt <mcpratt@...me>, saravanak@...gle.com, abel.vesa@...aro.org, alexander.stein@...tq-group.com, andriy.shevchenko@...ux.intel.com, bigunclemax@...il.com, brgl@...ev.pl, colin.foster@...advantage.com, djrscally@...il.com, dmitry.baryshkov@...aro.org, festevam@...il.com, fido_max@...ox.ru, frowand.list@...il.com, geert@...ux-m68k.org, heikki.krogerus@...ux.intel.com, kernel@...gutronix.de, linus.walleij@...aro.org, linux@...ck-us.net, luca.weiss@...rphone.com, magnus.damm@...il.com, martin.kepplinger@...i.sm, miquel.raynal@...tlin.com, rafal@...ecki.pl, ansuelsmth@...il.com, richard@....at, sakari.ailus@...ux.intel.com, sudeep.holla@....com, tglx@...utronix.de, tony@...mide.com, vigneshr@...com, dianders@...omium.org, jpb@...nel.org, rafael@...nel.org
Subject: [PATCH v1 2/4] driver core: fw_devlink: Link to supplier ancestor if no device
Driver core currently supports linking to the next parent fwnode,
but is not yet handling cases where that parent
is also a firmware child node not representing a real device,
which can lead to an indefinite deferred probe in some cases.
In this case, the fwnode that should actually be linked to
is multiple ancestors up which presents a challenge where
it is unknown how many ancestors up the node that
represents the real probing device is. This makes the usage of
fwnode_get_next_parent_dev() insufficient because the real device's
fwnode may or may not be an ancestor of the next parent fwnode as well.
Introduce flag FWNODE_FLAG_PARENT_IS_DEV
in order to mark child firmware nodes of a device
as having a parent device that can probe.
Allow fwnode link creation to the original supplier fwnode's ancestors
when the original supplier fwnode and any fwnodes in between are flagged
as FWNODE_FLAG_NOT_DEVICE and/or FWNODE_FLAG_PARENT_IS_DEV
with a new function __fwnode_link_add_parents() which then creates
the fwnode link to a real device that provides the supplier's function.
This depends on other functions to label a supplier fwnode
as not a real device, which must be done before the fwnode links
are created, and if after that, relevant links to the supplier
would have to be deleted and have links recreated, otherwise,
the fwnode link would be dropped before the device link is attempted
or a fwnode link would not be able to become a device link at all,
because they were created before these fwnode flags can have any effect.
It also depends on the supplier device to actually probe first
in order to have the fwnode flags in place to know for certain
which fwnodes are non-probing child nodes
of the fwnode for the supplier device.
The use case of function __fw_devlink_pickup_dangling_consumers()
is designed so that the parameters are always a supplier fwnode
and one of it's parent fwnodes, so it is safer to assume and more specific
that the flag PARENT_IS_DEV should be added there, rather than
declaring the original supplier fwnode as NOT_DEVICE at that point.
Because this function is called when the real supplier device probes
and recursively calls itself for all child nodes of the device's fwnode,
set the new flag here in order to let it propagate down
to all descendant nodes, thereby providing the info needed later
in order to link to the proper fwnode representing the supplier device.
If a fwnode is flagged as FWNODE_FLAG_NOT_DEVICE
by the time a device link is to be made with it,
but not flagged as FWNODE_FLAG_PARENT_IS_DEV,
the link is dropped, otherwise the device link
is still made with the original supplier fwnode.
Theoretically, we can also handle linking to an ancestor
of the supplier fwnode when forming device links, but there
are still cases where the necessary fwnode flags are still missing
because the real supplier device did not probe yet.
Signed-off-by: Michael Pratt <mcpratt@...me>
---
drivers/base/core.c | 49 ++++++++++++++++++++++++++++++++++++------
include/linux/fwnode.h | 4 ++++
2 files changed, 47 insertions(+), 6 deletions(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index c05a5f6b0641..7f2652cf5edc 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -92,13 +92,45 @@ static int __fwnode_link_add(struct fwnode_handle *con,
return 0;
}
+static int __fwnode_link_add_parents(struct fwnode_handle *con,
+ struct fwnode_handle *sup,
+ u8 flags, bool loop)
+{
+ int ret = -EINVAL;
+ struct fwnode_handle *parent;
+
+ fwnode_for_each_parent_node(sup, parent) {
+ /* Ignore the root node */
+ if (fwnode_count_parents(parent) &&
+ fwnode_device_is_available(parent) &&
+ !(parent->flags & FWNODE_FLAG_NOT_DEVICE) &&
+ !(parent->flags & FWNODE_FLAG_PARENT_IS_DEV)) {
+ ret = __fwnode_link_add(con, parent, flags);
+ }
+
+ if (!loop && !ret) {
+ fwnode_handle_put(parent);
+ return 0;
+ }
+ }
+
+ return ret;
+}
+
int fwnode_link_add(struct fwnode_handle *con, struct fwnode_handle *sup)
{
int ret;
mutex_lock(&fwnode_link_lock);
- ret = __fwnode_link_add(con, sup, 0);
+
+ if ((sup->flags & FWNODE_FLAG_NOT_DEVICE) &&
+ (sup->flags & FWNODE_FLAG_PARENT_IS_DEV))
+ ret = __fwnode_link_add_parents(con, sup, 0, false);
+ else
+ ret = __fwnode_link_add(con, sup, 0);
+
mutex_unlock(&fwnode_link_lock);
+
return ret;
}
@@ -218,7 +250,8 @@ static void __fwnode_links_move_consumers(struct fwnode_handle *from,
* MANAGED device links to this device, so leave @fwnode and its descendant's
* fwnode links alone.
*
- * Otherwise, move its consumers to the new supplier @new_sup.
+ * Otherwise, flag descendants of @fwnode as having a parent fwnode for a device
+ * that has probed and move bad fwnode consumer links from @fwnode to @new_sup.
*/
static void __fw_devlink_pickup_dangling_consumers(struct fwnode_handle *fwnode,
struct fwnode_handle *new_sup)
@@ -228,8 +261,11 @@ static void __fw_devlink_pickup_dangling_consumers(struct fwnode_handle *fwnode,
if (fwnode->dev && fwnode->dev->driver)
return;
- fwnode->flags |= FWNODE_FLAG_NOT_DEVICE;
- __fwnode_links_move_consumers(fwnode, new_sup);
+ if (fwnode->flags & FWNODE_FLAG_NOT_DEVICE)
+ __fwnode_links_move_consumers(fwnode, new_sup);
+
+ fwnode->flags |= FWNODE_FLAG_PARENT_IS_DEV;
+ new_sup->flags &= ~(FWNODE_FLAG_PARENT_IS_DEV);
fwnode_for_each_available_child_node(fwnode, child)
__fw_devlink_pickup_dangling_consumers(child, new_sup);
@@ -2071,8 +2107,9 @@ static int fw_devlink_create_devlink(struct device *con,
device_links_write_unlock();
}
- if (sup_handle->flags & FWNODE_FLAG_NOT_DEVICE)
- sup_dev = fwnode_get_next_parent_dev(sup_handle);
+ if ((sup_handle->flags & FWNODE_FLAG_NOT_DEVICE) &&
+ !(sup_handle->flags & FWNODE_FLAG_PARENT_IS_DEV))
+ return -EINVAL;
else
sup_dev = get_dev_from_fwnode(sup_handle);
diff --git a/include/linux/fwnode.h b/include/linux/fwnode.h
index 2a72f55d26eb..3ed8ba503062 100644
--- a/include/linux/fwnode.h
+++ b/include/linux/fwnode.h
@@ -30,6 +30,9 @@ struct device;
* BEST_EFFORT: The fwnode/device needs to probe early and might be missing some
* suppliers. Only enforce ordering with suppliers that have
* drivers.
+ * PARENT_IS_DEV: The fwnode is a child of a fwnode that is or will be populated as a
+ * struct device, which is more suitable for device links
+ * than the fwnode child which may never have a struct device.
*/
#define FWNODE_FLAG_LINKS_ADDED BIT(0)
#define FWNODE_FLAG_NOT_DEVICE BIT(1)
@@ -37,6 +40,7 @@ struct device;
#define FWNODE_FLAG_NEEDS_CHILD_BOUND_ON_ADD BIT(3)
#define FWNODE_FLAG_BEST_EFFORT BIT(4)
#define FWNODE_FLAG_VISITED BIT(5)
+#define FWNODE_FLAG_PARENT_IS_DEV BIT(6)
struct fwnode_handle {
struct fwnode_handle *secondary;
--
2.30.2
Powered by blists - more mailing lists