From: Andrew Lunn <andrew@lunn.ch>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Daniel Golle <daniel@makrotopia.org>,
Hauke Mehrtens <hauke@hauke-m.de>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Rasmus Villemoes <ravi@prevas.dk>,
"Benny (Ying-Tsan) Weng" <yweng@maxlinear.com>,
John Crispin <john@phrozen.org>
Subject: Re: [PATCH net v3] net: dsa: mxl-gsw1xx: manually clear RANEG bit
Date: Mon, 8 Dec 2025 14:37:38 +0100 [thread overview]
Message-ID: <586e6fe2-60af-4a8f-9727-98ad7d6b9593@lunn.ch> (raw)
In-Reply-To: <aTbI99uWvg08wgV9@shell.armlinux.org.uk>
On Mon, Dec 08, 2025 at 12:47:51PM +0000, Russell King (Oracle) wrote:
> On Mon, Dec 08, 2025 at 01:27:04AM +0000, Daniel Golle wrote:
> > static void gsw1xx_remove(struct mdio_device *mdiodev)
> > {
> > struct gswip_priv *priv = dev_get_drvdata(&mdiodev->dev);
> > + struct gsw1xx_priv *gsw1xx_priv;
> >
> > if (!priv)
> > return;
> >
> > + gsw1xx_priv = container_of(priv, struct gsw1xx_priv, gswip);
> > + cancel_delayed_work_sync(&gsw1xx_priv->clear_raneg);
> > +
> > gswip_disable_switch(priv);
> >
> > dsa_unregister_switch(priv->ds);
>
> Can we please pay attention to ->remove methods, and code them properly
> please?
>
> There are two golden rules of driver programming.
>
> 1. Do not publish the device during probe until hardware setup is
> complete. If you publish before hardware setup is complete, userspace
> is free to race with the hardware setup and start using the device.
> This is especially true of recent systems which use hotplug events
> via udev and systemd to do stuff.
>
> 2. Do not start tearing down a device until the user interfaces have
> been unpublished. Similar to (1), while the user interface is
> published, uesrspace is completely free to interact with the device
> in any way it sees fit.
>
> In this case, what I'm concerned with is the call above to
> cancel_delayed_work_sync() before dsa_unregister_switch(). While
> cancel_delayed_work_sync() will stop this work and wait for the handler
> to finish running before returning (which is safe) there is a window
> between this call and dsa_unregister_switch() where the user _could_
> issue a badly timed ethtool command which invokes
> gsw1xx_pcs_an_restart(), which would re-schedule the delayed work,
> thus undoing the cancel_delayed_work_sync() effect in this path.
And this is why is was pushing for the much simpler msleep(10), or
io_poll.h polling to see if it self clears. It is hard to get that
wrong, where as delayed work is much easier to get wrong.
Andrew
next prev parent reply other threads:[~2025-12-08 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 1:27 Daniel Golle
2025-12-08 12:47 ` Russell King (Oracle)
2025-12-08 13:37 ` Andrew Lunn [this message]
2025-12-08 15:52 ` Russell King (Oracle)
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=586e6fe2-60af-4a8f-9727-98ad7d6b9593@lunn.ch \
--to=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=ravi@prevas.dk \
--cc=yweng@maxlinear.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
all inboxes | Powered by JetHome®