netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Xuanqiang Luo <xuanqiang.luo@linux.dev>,
	netdev@vger.kernel.org, andrew@lunn.ch, kuba@kernel.org
Cc: hkallweit1@gmail.com, chleroy@kernel.org,
	qingfang.deng@siflower.com.cn, hao.guan@siflower.com.cn,
	linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, linux-kernel@vger.kernel.org,
	Xuanqiang Luo <luoxuanqiang@kylinos.cn>
Subject: Re: [PATCH net v5 2/6] net: phy: unregister SFP upstream before port cleanup
Date: Mon, 31 Aug 2026 09:58:42 +0200	[thread overview]
Message-ID: <b5680417-53e6-4a87-861e-40765a6ccada@bootlin.com> (raw)
In-Reply-To: <20260823035600.188864-3-xuanqiang.luo@linux.dev>

Hi,

On 8/23/26 05:55, Xuanqiang Luo wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
> 
> Commit 4497f5028675 ("net: phy: Clean the phy_ports after unregistering
> the downstream SFP bus") established that an SFP upstream must be
> unregistered before its phy_ports are destroyed because SFP callbacks
> may access these ports.
> 
> phy_setup_ports() does not follow this order when a later port setup
> step fails after phy_sfp_probe() succeeds. It destroys the SFP phy_port
> and leaves phy_probe() to unregister the upstream later, creating a race
> between port destruction and SFP upstream callbacks.
> 
> The error unwind is also split across three functions. If
> phy_setup_sfp_port() fails, phy_sfp_probe() leaves the upstream
> registered and relies on phy_probe() to remove it after
> phy_setup_ports() returns.
> 
> Make each layer unwind the resources it successfully set up. Unregister
> only the upstream in phy_sfp_probe() when SFP port setup fails, since
> the failed port has already been destroyed. Add phy_sfp_release() for a
> successful SFP probe, and make phy_setup_ports() use it before cleaning
> up the remaining ports. Once phy_setup_ports() has rolled back all port
> setup, make phy_probe() skip this cleanup.
> 
> Fixes: 589e934d2735 ("net: phy: Introduce PHY ports representation")
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Xuanqiang Luo <luoxuanqiang@kylinos.cn>

Thanks for this cleanup,

Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>

Maxime

> ---
>  drivers/net/phy/phy_device.c | 49 ++++++++++++++++++++++++++++--------
>  1 file changed, 38 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
> index 2cf70471ae089..4b9b2300422fb 100644
> --- a/drivers/net/phy/phy_device.c
> +++ b/drivers/net/phy/phy_device.c
> @@ -1723,12 +1723,41 @@ static int phy_sfp_probe(struct phy_device *phydev)
>  			phydev->sfp_bus = NULL;
>  	}
>  
> -	if (!ret && phydev->sfp_bus)
> +	if (!ret && phydev->sfp_bus) {
>  		ret = phy_setup_sfp_port(phydev);
> +		if (ret) {
> +			sfp_bus_del_upstream(phydev->sfp_bus);
> +			phydev->sfp_bus = NULL;
> +		}
> +	}
>  
>  	return ret;
>  }
>  
> +/**
> + * phy_sfp_release - release resources set up by phy_sfp_probe()
> + * @phydev: the PHY device
> + *
> + * Release the SFP resources set up by a successful phy_sfp_probe(). Unregister
> + * the upstream before destroying its phy_port, so SFP upstream callbacks cannot
> + * race with port destruction.
> + */
> +static void phy_sfp_release(struct phy_device *phydev)
> +{
> +	struct phy_port *port, *tmp;
> +
> +	sfp_bus_del_upstream(phydev->sfp_bus);
> +	phydev->sfp_bus = NULL;
> +
> +	list_for_each_entry_safe(port, tmp, &phydev->ports, head) {
> +		if (!port->is_sfp)
> +			continue;
> +
> +		phy_del_port(phydev, port);
> +		phy_port_destroy(port);
> +	}
> +}
> +
>  static bool phy_drv_supports_irq(const struct phy_driver *phydrv)
>  {
>  	return phydrv->config_intr && phydrv->handle_interrupt;
> @@ -3547,13 +3576,13 @@ static int phy_setup_ports(struct phy_device *phydev)
>  	if (!phydev->is_genphy_driven) {
>  		ret = phy_sfp_probe(phydev);
>  		if (ret)
> -			goto out;
> +			goto err_ports;
>  	}
>  
>  	if (phydev->n_ports < phydev->max_n_ports) {
>  		ret = phy_default_setup_single_port(phydev);
>  		if (ret)
> -			goto out;
> +			goto err_sfp;
>  	}
>  
>  	linkmode_zero(ports_supported);
> @@ -3580,7 +3609,9 @@ static int phy_setup_ports(struct phy_device *phydev)
>  
>  	return 0;
>  
> -out:
> +err_sfp:
> +	phy_sfp_release(phydev);
> +err_ports:
>  	phy_cleanup_ports(phydev);
>  	return ret;
>  }
> @@ -3744,7 +3775,7 @@ static int phy_probe(struct device *dev)
>  
>  	err = phy_setup_ports(phydev);
>  	if (err)
> -		goto out_sfp_release;
> +		goto out_reset;
>  
>  	phy_advertise_supported(phydev);
>  
> @@ -3816,9 +3847,7 @@ static int phy_probe(struct device *dev)
>  		phy_led_triggers_unregister(phydev);
>  
>  out_sfp_release:
> -	sfp_bus_del_upstream(phydev->sfp_bus);
> -	phydev->sfp_bus = NULL;
> -
> +	phy_sfp_release(phydev);
>  	phy_cleanup_ports(phydev);
>  
>  out_reset:
> @@ -3842,9 +3871,7 @@ static int phy_remove(struct device *dev)
>  
>  	phydev->state = PHY_DOWN;
>  
> -	sfp_bus_del_upstream(phydev->sfp_bus);
> -	phydev->sfp_bus = NULL;
> -
> +	phy_sfp_release(phydev);
>  	phy_cleanup_ports(phydev);
>  
>  	if (phydev->drv && phydev->drv->remove)


  reply	other threads:[~2026-08-31  7:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23  3:55 [PATCH net v5 0/6] net: phy: fix cleanup after probe failure Xuanqiang Luo
2026-08-23  3:55 ` [PATCH net v5 1/6] net: phy: split phy_probe() error paths Xuanqiang Luo
2026-08-31  7:58   ` Maxime Chevallier
2026-08-23  3:55 ` [PATCH net v5 2/6] net: phy: unregister SFP upstream before port cleanup Xuanqiang Luo
2026-08-31  7:58   ` Maxime Chevallier [this message]
2026-08-23  3:55 ` [PATCH net v5 3/6] net: phy: set PHY_READY after LED setup Xuanqiang Luo
2026-08-23  3:55 ` [PATCH net v5 4/6] net: phy: call driver remove when core initialization fails Xuanqiang Luo
2026-08-23  3:55 ` [PATCH net v5 5/6] net: phy: propagate errors from default port setup Xuanqiang Luo
2026-08-23  3:56 ` [PATCH net v5 6/6] net: phy: avoid double-free after LED trigger registration failure Xuanqiang Luo
2026-08-27 11:40   ` Paolo Abeni
2026-08-31  0:30 ` [PATCH net v5 0/6] net: phy: fix cleanup after probe failure patchwork-bot+netdevbpf

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=b5680417-53e6-4a87-861e-40765a6ccada@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=chleroy@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hao.guan@siflower.com.cn \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luoxuanqiang@kylinos.cn \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qingfang.deng@siflower.com.cn \
    --cc=xuanqiang.luo@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).