From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
yijiangshan@kylinos.cn
Subject: Re: [PATCH net] net: avoid theoretical races with ref drain
Date: Thu, 06 Aug 2026 16:50:25 +0000 [thread overview]
Message-ID: <178603502513.1375455.12453285964072800716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806022821.2079945-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 5 Aug 2026 19:28:21 -0700 you wrote:
> Technically, it's illegal to take a ref on a netdev just because
> we have a pointer on which we already hold a ref, with no other
> protection. This is because our simple per-cpu refcount
> implementation cannot atomically read the count.
>
> Let's make sure we cancel outstanding work and never queue more
> work for a device we know is dead. This way taking a ref on
> a dev we know is on the netdev_work_list is always going to be safe.
>
> [...]
Here is the summary with links:
- [net] net: avoid theoretical races with ref drain
https://git.kernel.org/netdev/net/c/d31c14e56a4f
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-08-06 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 2:28 [PATCH net] net: avoid theoretical races with ref drain Jakub Kicinski
2026-08-06 16:50 ` 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=178603502513.1375455.12453285964072800716.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yijiangshan@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.