From: Aleksei Sviridkin <f@lex.la>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Woojung Huh <woojung.huh@microchip.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: [PATCH net-next v4 4/4] net: phy: make an unbind wait for the attached consumer to detach
Date: Thu, 1 Oct 2026 16:01:20 +0300 [thread overview]
Message-ID: <20261001130120.104628-5-f@lex.la> (raw)
In-Reply-To: <20261001130120.104628-1-f@lex.la>
With attach serialised against unbind, the unbind that loses the race
waits for the attach and then removes the driver from a PHY that is now
attached. phylink uses phydev->drv right after the attach returns, and
phylib uses it again in later phy_start(), phy_stop() and state machine
runs.
Found on the same KN-1012 by repeating the wan race on a kernel with
the previous patch. The attach completed, the unbind then removed the
driver, and phylink faulted one frame up:
Unable to handle kernel access to user memory outside uaccess
routines at virtual address 00000000000000a0
Comm: ip
Call trace:
phylink_bringup_phy+0x680/0x784 (P)
phylink_fwnode_phy_connect+0x1b8/0x27c
phylink_of_phy_connect+0x18/0x20
mtk_open+0x38/0xb70
A DSA port gets there without any race, and did on the same board
before this series: unbinding the lan4 PHY driver returns at once, and
with lan4 up, tearing the switch down later faults in
_phy_state_machine(), called by phy_stop() from dsa_user_close().
The driver core gives a driver no way to refuse an unbind, so make
phy_remove() wait until phy_detach() has run. An unbind of a PHY in use
now blocks until the consumer lets go: ifdown for a MAC that connects
in ndo_open, the switch teardown for DSA, which connects at probe.
Deleting the PHY device through phy_device_remove(), as
mdiobus_unregister() does, keeps today's behaviour and does not wait,
and it releases an unbind that is already waiting. Some MAC drivers
unregister their MDIO bus with the PHY still attached and never detach
it (greth), so waiting there would hang their removal for good.
Fixes: 00db8189d984 ("This patch adds a PHY Abstraction Layer to the Linux Kernel, enabling ethernet drivers to remain as ignorant as is reasonable of the connected PHY's design and operation details.")
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
---
Changes in v4:
- Rebased on net-next. A line over 80 columns wrapped.
drivers/net/phy/phy_device.c | 22 ++++++++++++++++++++++
include/linux/phy.h | 4 ++++
2 files changed, 26 insertions(+)
diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
index 544b2da6a1d9..8a7cd53f9a14 100644
--- a/drivers/net/phy/phy_device.c
+++ b/drivers/net/phy/phy_device.c
@@ -1065,6 +1065,13 @@ void phy_device_remove(struct phy_device *phydev)
unregister_mii_timestamper(phydev->mii_ts);
pse_control_put(phydev->psec);
+ mutex_lock(&phydev->bind_lock);
+ phydev->removing = true;
+ mutex_unlock(&phydev->bind_lock);
+ /* Order the store before waking an unbind waiting in phy_remove() */
+ smp_mb();
+ wake_up_var(&phydev->attached);
+
device_del(&phydev->mdio.dev);
/* Assert the reset signal */
@@ -1737,6 +1744,8 @@ static void phy_detach_internal(struct phy_device *phydev, bool notify_bus)
module_put(phydev->drv_owner);
phydev->drv_owner = NULL;
+ store_release_wake_up(&phydev->attached, false);
+
/* If the device had no specific driver before (i.e. - it
* was using the generic driver), we unbind the device
* from the generic driver so that there's a chance a
@@ -1940,6 +1949,7 @@ int phy_attach_direct(struct net_device *dev, struct phy_device *phydev,
phy_resume(phydev);
+ phydev->attached = true;
mutex_unlock(&phydev->bind_lock);
/**
@@ -3843,11 +3853,23 @@ static int phy_probe(struct device *dev)
static int phy_remove(struct device *dev)
{
struct phy_device *phydev = to_phy_device(dev);
+ bool attached;
mutex_lock(&phydev->bind_lock);
phydev->bound = false;
+ attached = phydev->attached && !phydev->removing;
mutex_unlock(&phydev->bind_lock);
+ /* The driver core cannot refuse an unbind, and the consumer keeps
+ * using phydev->drv until it detaches.
+ */
+ if (attached) {
+ phydev_warn(phydev, "unbind waits for the PHY to be detached\n");
+ wait_var_event(&phydev->attached,
+ !READ_ONCE(phydev->attached) ||
+ READ_ONCE(phydev->removing));
+ }
+
cancel_delayed_work_sync(&phydev->state_queue);
if (IS_ENABLED(CONFIG_PHYLIB_LEDS) && !phy_driver_is_genphy(phydev))
diff --git a/include/linux/phy.h b/include/linux/phy.h
index 3881a4651da0..1b7e7bf124cc 100644
--- a/include/linux/phy.h
+++ b/include/linux/phy.h
@@ -673,6 +673,8 @@ struct phy_oatc14_sqi_capability {
* @lock: Mutex for serialization access to PHY
* @bind_lock: Serialises attach and detach with driver bind and unbind
* @bound: A driver has finished probing and is not being removed
+ * @attached: phy_attach_direct() succeeded and phy_detach() has not run
+ * @removing: phy_device_remove() is deleting the device
* @state_queue: Work queue for state machine
* @link_down_events: Number of times link was lost
* @shared: Pointer to private data shared by phys in one package
@@ -807,6 +809,8 @@ struct phy_device {
/* Protects bound */
struct mutex bind_lock;
bool bound;
+ bool attached;
+ bool removing;
/* This may be modified under the rtnl lock */
bool sfp_bus_attached;
--
2.53.0
next prev parent reply other threads:[~2026-10-01 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:01 [PATCH net-next v4 0/4] net: phy: make PHY driver unbind safe against attach and use Aleksei Sviridkin
2026-10-01 13:01 ` [PATCH net-next v4 1/4] net: phy: refuse a second attach before touching the PHY Aleksei Sviridkin
2026-10-05 13:01 ` netdev-bot+sashiko
2026-10-01 13:01 ` [PATCH net-next v4 2/4] net: phy: put the driver module the attach took Aleksei Sviridkin
2026-10-05 13:01 ` netdev-bot+sashiko
2026-10-01 13:01 ` [PATCH net-next v4 3/4] net: phy: serialise attach and detach with PHY driver bind and unbind Aleksei Sviridkin
2026-10-05 13:01 ` netdev-bot+sashiko
2026-10-01 13:01 ` Aleksei Sviridkin [this message]
2026-10-05 13:01 ` [PATCH net-next v4 4/4] net: phy: make an unbind wait for the attached consumer to detach netdev-bot+sashiko
2026-10-06 11:30 ` Aleksei Sviridkin
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=20261001130120.104628-5-f@lex.la \
--to=f@lex.la \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=woojung.huh@microchip.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