From: Carlo Szelinsky <github@szelinsky.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Kory Maincent <kory.maincent@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Kyle Swenson <kyle.swenson@est.tech>, Ross Cawston <ross@r-sc.ca>,
netdev-bot+sashiko@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Carlo Szelinsky <github@szelinsky.de>
Subject: [PATCH net v2 05/14] net: pse-pd: do not reach a freed PHY from the notification worker
Date: Tue, 20 Oct 2026 19:12:40 +0200 [thread overview]
Message-ID: <20261020171249.853085-6-github@szelinsky.de> (raw)
In-Reply-To: <20261020171249.853085-1-github@szelinsky.de>
The notification worker holds a reference on the pse_control, but not
on the PHY that psec->attached_phydev points to. If the PHY is removed
while the worker runs, the pse_control survives and the worker reads the
freed PHY. The same happens without a race when two PHYs share one PI:
attached_phydev keeps pointing at the first PHY after it is removed.
pse_control_put() unlinks and frees a pse_control under pse_list_mutex,
and phy_device_remove() calls it before the PHY is freed. So instead of
taking a reference, let the worker look the pse_control up and use
attached_phydev under pse_list_mutex. This nests pse_list_mutex inside
rtnl; nothing under pse_list_mutex takes rtnl.
For a PI shared by two PHYs there is no single netdev to report to, so
clear attached_phydev when a second PHY takes the pse_control, and warn.
Events for that PI are then no longer reported, even after one PHY goes
away. Failing the second PHY instead would fail its whole MDIO bus.
Triggered in QEMU (arm64, KASAN) with a test-only PSE controller:
removing a PHY while the worker waits for rtnl, and removing one of
two PHYs on a shared PI, both give
BUG: KASAN: slab-use-after-free in pse_send_ntf_worker+0x2b0/0x2bc
With this patch both are gone.
Fixes: fc0e6db30941 ("net: pse-pd: Add support for reporting events")
Signed-off-by: Carlo Szelinsky <github@szelinsky.de>
---
drivers/net/pse-pd/pse_core.c | 44 ++++++++++++++++++++++++++---------
1 file changed, 33 insertions(+), 11 deletions(-)
diff --git a/drivers/net/pse-pd/pse_core.c b/drivers/net/pse-pd/pse_core.c
index eab7e25f2039..af9eb2979270 100644
--- a/drivers/net/pse-pd/pse_core.c
+++ b/drivers/net/pse-pd/pse_core.c
@@ -238,24 +238,22 @@ static int of_load_pse_pis(struct pse_controller_dev *pcdev)
* @pcdev: a pointer to the PSE
* @id: index of the PSE control
*
- * Return: pse_control pointer or NULL. The device returned has had a
- * reference added and the pointer is safe until the user calls
- * pse_control_put() to indicate they have finished with it.
+ * Must be called with pse_list_mutex held. No reference is taken: the
+ * pointer is only valid until pse_list_mutex is released.
+ *
+ * Return: pse_control pointer or NULL.
*/
static struct pse_control *
pse_control_find_by_id(struct pse_controller_dev *pcdev, int id)
{
struct pse_control *psec;
- mutex_lock(&pse_list_mutex);
+ lockdep_assert_held(&pse_list_mutex);
+
list_for_each_entry(psec, &pcdev->pse_control_head, list) {
- if (psec->id == id) {
- kref_get(&psec->refcnt);
- mutex_unlock(&pse_list_mutex);
+ if (psec->id == id)
return psec;
- }
}
- mutex_unlock(&pse_list_mutex);
return NULL;
}
@@ -268,6 +266,7 @@ pse_control_find_by_id(struct pse_controller_dev *pcdev, int id)
static struct net_device *pse_control_get_netdev(struct pse_control *psec)
{
ASSERT_RTNL();
+ lockdep_assert_held(&pse_list_mutex);
if (!psec || !psec->attached_phydev)
return NULL;
@@ -1015,13 +1014,23 @@ static void pse_send_ntf_worker(struct work_struct *work)
struct net_device *netdev;
struct pse_control *psec;
- psec = pse_control_find_by_id(pcdev, ntf.id);
+ /* If attached_phydev is set, it names the only PHY that
+ * holds this pse_control: a second PHY on the same PI
+ * clears it in pse_control_get_internal(). That PHY's
+ * pse_control_put() unlinks and frees the pse_control under
+ * pse_list_mutex before the PHY itself can be freed. Holding
+ * the mutex across the lookup and the attached_phydev
+ * dereference therefore keeps the PHY alive, which a
+ * reference on the pse_control alone would not.
+ */
rtnl_lock();
+ mutex_lock(&pse_list_mutex);
+ psec = pse_control_find_by_id(pcdev, ntf.id);
netdev = pse_control_get_netdev(psec);
if (netdev)
ethnl_pse_send_ntf(netdev, ntf.notifs);
+ mutex_unlock(&pse_list_mutex);
rtnl_unlock();
- pse_control_put(psec);
}
}
@@ -1412,6 +1421,19 @@ pse_control_get_internal(struct pse_controller_dev *pcdev, unsigned int index,
list_for_each_entry(psec, &pcdev->pse_control_head, list) {
if (psec->id == index) {
+ /* attached_phydev can only name one PHY. If a second
+ * one shares the PI, either may be removed first and
+ * leave it pointing at a freed phy_device, so stop
+ * reporting events for this PI instead.
+ */
+ if (psec->attached_phydev &&
+ psec->attached_phydev != phydev) {
+ dev_warn(pcdev->dev,
+ "PI %u shared by several PHYs, not reporting its events\n",
+ index);
+ psec->attached_phydev = NULL;
+ }
+
kref_get(&psec->refcnt);
return psec;
}
--
2.43.0
next prev parent reply other threads:[~2026-10-20 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 17:12 [PATCH net v2 00/14] net: pse-pd: assorted lifetime and error-path fixes Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 01/14] net: pse-pd: size the notification kfifo after defaulting nr_lines Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 02/14] net: pse-pd: remove dead pi_get_admin_state() checks Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 03/14] net: pse-pd: fix module refcount leak in pse_control_get_internal() Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 04/14] net: pse-pd: do not keep a failed IRQ in pcdev->irq Carlo Szelinsky
2026-10-20 17:12 ` Carlo Szelinsky [this message]
2026-10-20 17:12 ` [PATCH net v2 06/14] net: pse-pd: check the PI state under the lock when setting a power limit Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 07/14] net: pse-pd: do not tie a shared power domain to its creator's devres Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 08/14] net: pse-pd: stop async event sources before freeing PI data in unregister Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 09/14] net: pse-pd: unregister from the controller list before freeing PI data Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 10/14] net: pse-pd: keep the PI data until the PI regulators are gone Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 11/14] net: pse-pd: unwind allocations when controller registration fails Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 12/14] net: pse-pd: use each PI's own supply handle for the power budget Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 13/14] net: pse-pd: pd692x0: release the manager power budget through devres Carlo Szelinsky
2026-10-20 17:12 ` [PATCH net v2 14/14] net: pse-pd: pd692x0: defer probe while a manager supply is unresolved Carlo Szelinsky
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=20261020171249.853085-6-github@szelinsky.de \
--to=github@szelinsky.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=kyle.swenson@est.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=ross@r-sc.ca \
/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.