From: Karl Mehltretter <kmehltretter@gmail.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: netdev@vger.kernel.org, Roger Quadros <rogerq@kernel.org>,
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>, Keerthy <j-keerthy@ti.com>,
Kevin Hao <haokexin@gmail.com>,
Alexander Sverdlin <alex@sverdlin.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: cpsw: fix netdev cleanup on probe failure
Date: Mon, 19 Oct 2026 22:37:17 +0200 [thread overview]
Message-ID: <atZ8lCW0VVPzoHwb@gmail.com> (raw)
In-Reply-To: <c20d708a-f4d6-4e66-a516-056d93264825@ti.com>
On Mon, Oct 19, 2026 at 12:19:11PM +0100, Siddharth Vadapalli wrote:
> > + unregister_netdev(ndev);
> > + disable_work_sync(&priv->rx_mode_work);
>
> Although the above code is a refactor, it appears to me that the correct
> sequence should be:
> disable_work_sync(&priv->rx_mode_work);
> unregister_netdev(ndev);
> RX Mode work (cpsw_ndo_set_rx_mode_work) does have a 'netif_running' check
> so it might still be fine if the sequence isn't followed.
>
> Please correct me if I am mistaken regarding the above. Rest of the patch
> looks good to me.
>
Both orders are safe here. The worker and unregister_netdev() serialize
on RTNL, so a worker running after unregister exits at !netif_running().
This matches cpsw_new, so I'd keep the current order.
Thanks,
Karl
next prev parent reply other threads:[~2026-10-19 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 6:04 Karl Mehltretter
2026-10-19 6:49 ` Siddharth Vadapalli
2026-10-19 20:37 ` Karl Mehltretter [this message]
2026-10-19 7:24 ` Sverdlin, Alexander
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=atZ8lCW0VVPzoHwb@gmail.com \
--to=kmehltretter@gmail.com \
--cc=alex@sverdlin.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=haokexin@gmail.com \
--cc=j-keerthy@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=stable@vger.kernel.org \
/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®