From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Woojung Huh <woojung.huh@microchip.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King <rmk+kernel@armlinux.org.uk>,
Thangaraj Samynathan <Thangaraj.S@microchip.com>,
Rengarajan Sundararajan <Rengarajan.S@microchip.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
Phil Elwell <phil@raspberrypi.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next v1 1/1] net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect
Date: Mon, 23 Jun 2025 16:55:37 -0700 [thread overview]
Message-ID: <20250623165537.53558fdb@kernel.org> (raw)
In-Reply-To: <20250620085144.1858723-1-o.rempel@pengutronix.de>
On Fri, 20 Jun 2025 10:51:44 +0200 Oleksij Rempel wrote:
> A WARN may be triggered in __netif_napi_del_locked() during USB device
> disconnect:
>
> WARNING: CPU: 0 PID: 11 at net/core/dev.c:7417 __netif_napi_del_locked+0x2b4/0x350
>
> This occurs because NAPI remains enabled when the device is unplugged and
> teardown begins. While `napi_disable()` was previously called in the
> `lan78xx_stop()` path, that function is not invoked on disconnect. Instead,
> when using PHYLINK, the `mac_link_down()` callback is guaranteed to run
> during disconnect, making it the correct place to disable NAPI.
>
> Similarly, move `napi_enable()` to `mac_link_up()` to pair the lifecycle
> with actual MAC state.
Stopping and starting NAPI on link events is pretty unusual.
The problem is the disconnect handling, unregistering netdev
removes the NAPIs automatically, I think all you need is to
remove the explicit netif_napi_del() in lan78xx_disconnect().
Core will call _stop (which disables the NAPI), and then
it will del the NAPI.
> This patch is intended for `net-next` since the issue existed before the
> PHYLINK migration, but is more naturally and cleanly addressed now that
> PHYLINK manages link state transitions.
And repost that for net, please.. :)
--
pw-bot: cr
next prev parent reply other threads:[~2025-06-23 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 8:51 Oleksij Rempel
2025-06-23 23:55 ` Jakub Kicinski [this message]
2025-06-26 10:18 ` Oleksij Rempel
2025-06-26 18:29 ` Jakub Kicinski
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=20250623165537.53558fdb@kernel.org \
--to=kuba@kernel.org \
--cc=Rengarajan.S@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=phil@raspberrypi.org \
--cc=rmk+kernel@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®