From: Vineeth Karumanchi <vineeth.karumanchi@amd.com>
To: <theo.lebrun@bootlin.com>, <conor.dooley@microchip.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <vineeth.karumanchi@amd.com>, <git@amd.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH net-next] net: macb: detach netdev before closing on shutdown
Date: Tue, 1 Sep 2026 19:55:40 +0530 [thread overview]
Message-ID: <20260901142541.1469544-1-vineeth.karumanchi@amd.com> (raw)
macb_shutdown() calls netif_device_detach() after dev_close().
netif_device_detach() only stops the TX queues when the device is
still running:
if (test_and_clear_bit(__LINK_STATE_PRESENT, &dev->state) &&
netif_running(dev))
netif_tx_stop_all_queues(dev);
By that point dev_close() has already cleared the running state, so the
detach only clears __LINK_STATE_PRESENT and the netif_tx_stop_all_queues()
step is skipped.
Reorder so the device is detached while still running, letting
netif_device_detach() mark it absent and stop the TX queues as intended,
before dev_close() tears the interface down.
This is a cleanup with no functional change: dev_close() stops the queues
and quiesces the DMA/HW via macb_close() regardless of ordering, so the
reboot/kexec safety path is unaffected.
Signed-off-by: Vineeth Karumanchi <vineeth.karumanchi@amd.com>
---
drivers/net/ethernet/cadence/macb_main.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c
index 76ee4f506033..21ebaee00f9e 100644
--- a/drivers/net/ethernet/cadence/macb_main.c
+++ b/drivers/net/ethernet/cadence/macb_main.c
@@ -6246,12 +6246,11 @@ static void macb_shutdown(struct platform_device *pdev)
struct net_device *netdev = platform_get_drvdata(pdev);
rtnl_lock();
+ netif_device_detach(netdev);
if (netif_running(netdev))
dev_close(netdev);
- netif_device_detach(netdev);
-
rtnl_unlock();
}
--
2.43.0
reply other threads:[~2026-09-01 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260901142541.1469544-1-vineeth.karumanchi@amd.com \
--to=vineeth.karumanchi@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=theo.lebrun@bootlin.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