From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, stable@vger.kernel.org,
syzbot+1269fe6cc2016008124e@syzkaller.appspotmail.com,
bsdhenrymartin@gmail.com, kuniyu@google.com,
namangulati@google.com, pablo@netfilter.org, fw@strlen.de
Subject: Re: [PATCH net] net: wait for in-flight device unregistrations before netns dismantle
Date: Tue, 10 Nov 2026 02:54:42 +0000 [thread overview]
Message-ID: <179427928217.3612825.16476819658097015103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105144543.1624238-1-edumazet@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Nov 2026 15:45:43 +0100 you wrote:
> A device can be unregistered by a context other than the cleanup_net()
> of its own netns, for instance a veth whose peer in another netns is
> deleted. If references on it are still held, it stays in
> netdev_wait_allrefs_any(), which rebroadcasts NETDEV_UNREGISTER every
> second.
>
> Meanwhile its netns can be dismantled: default_device_exit_batch()
> only takes care of devices still listed in the netns, then pernet exit
> handlers free their state, and finally struct net is freed while the
> device still points to it.
>
> [...]
Here is the summary with links:
- [net] net: wait for in-flight device unregistrations before netns dismantle
https://git.kernel.org/netdev/net/c/c164a431a646
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:[~2026-11-10 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 14:45 [PATCH net] net: wait for in-flight device unregistrations before netns dismantle Eric Dumazet
2026-11-05 21:27 ` Naman Gulati
2026-11-10 2:54 ` 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=179427928217.3612825.16476819658097015103.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bsdhenrymartin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=namangulati@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+1269fe6cc2016008124e@syzkaller.appspotmail.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