From: patchwork-bot+netdevbpf@kernel.org
To: luoguangfei <15388634752@163.com>
Cc: nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: macb: fix unregister_netdev call order in macb_remove() [v2]
Date: Fri, 22 Aug 2025 01:20:10 +0000 [thread overview]
Message-ID: <175582561025.1263133.13241944786966815629.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250818232527.1316-1-15388634752@163.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 19 Aug 2025 07:25:27 +0800 you wrote:
> When removing a macb device, the driver calls phy_exit() before
> unregister_netdev(). This leads to a WARN from kernfs:
>
> ------------[ cut here ]------------
> kernfs: can not remove 'attached_dev', no directory
> WARNING: CPU: 1 PID: 27146 at fs/kernfs/dir.c:1683
> Call trace:
> kernfs_remove_by_name_ns+0xd8/0xf0
> sysfs_remove_link+0x24/0x58
> phy_detach+0x5c/0x168
> phy_disconnect+0x4c/0x70
> phylink_disconnect_phy+0x6c/0xc0 [phylink]
> macb_close+0x6c/0x170 [macb]
> ...
> macb_remove+0x60/0x168 [macb]
> platform_remove+0x5c/0x80
> ...
>
> [...]
Here is the summary with links:
- net: macb: fix unregister_netdev call order in macb_remove() [v2]
https://git.kernel.org/netdev/net/c/2df84b42f155
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-22 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 23:25 luoguangfei
2025-08-22 1:20 ` patchwork-bot+netdevbpf [this message]
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=175582561025.1263133.13241944786966815629.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=15388634752@163.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.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®