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,
bobbyeshleman@meta.com, daniel@iogearbox.net,
razor@blackwall.org
Subject: Re: [PATCH net-next v3] netdev: avoid skipping objects on race with device disappearance
Date: Fri, 04 Sep 2026 23:20:16 +0000 [thread overview]
Message-ID: <178856401614.1013351.11404992028614421992.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903221154.3359889-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 3 Sep 2026 15:11:54 -0700 you wrote:
> If the currently dumped device disappears while we were mid-dump
> we will get the next device without resetting the sub-object ID.
> This is quite unlikely, it was reported by an AI tool not a real
> user. Let's fix it for better dump consistency.
>
> We only intend to cover the case where device A disappears
> and we skip over sub-objects of device B which was stable (B existed
> before and after the dump). We don't intend to provide stable
> results for any device that gets created or deleted during
> the dump.
>
> [...]
Here is the summary with links:
- [net-next,v3] netdev: avoid skipping objects on race with device disappearance
https://git.kernel.org/netdev/net-next/c/761ae184f850
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-09-04 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 22:11 [PATCH net-next v3] netdev: avoid skipping objects on race with device disappearance Jakub Kicinski
2026-09-03 23:08 ` Eric Dumazet
2026-09-03 23:32 ` Jakub Kicinski
2026-09-04 23: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=178856401614.1013351.11404992028614421992.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bobbyeshleman@meta.com \
--cc=daniel@iogearbox.net \
--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=razor@blackwall.org \
/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