From: patchwork-bot+netdevbpf@kernel.org
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, deliran@verdict.gg, donald.hunter@gmail.com,
amcohen@nvidia.com, roopa@nvidia.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/3] ipv4: handle nexthop group shrink races
Date: Tue, 06 Oct 2026 23:30:10 +0000 [thread overview]
Message-ID: <179132941041.2826662.12574878292005935947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1790915964.git.4ncienth@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 2 Oct 2026 13:50:57 +0900 you wrote:
> fib_info_num_path() and fib_info_nhc() can observe different RCU
> generations of a replaceable nexthop group. An indexed consumer can
> therefore accept an index from a larger group and receive NULL after a
> concurrent shrink.
>
> Patch 1 is unchanged from v1. Patch 2 addresses the analogous
> fib_dump_info_fnhe() race Ido identified. Auditing the remaining
> accessor pairs found the same issue in the RCU-only hardware-flag
> notification path, fixed by patch 3. Separate patches retain the
> correct Fixes tag for each concurrency boundary.
>
> [...]
Here is the summary with links:
- [net,v2,1/3] ipv4: stop PMTU walk when nexthop group shrinks
https://git.kernel.org/netdev/net/c/6619e01855e6
- [net,v2,2/3] ipv4: stop exception dump when nexthop group shrinks
https://git.kernel.org/netdev/net/c/4f4afc07dcb2
- [net,v2,3/3] ipv4: stop route notification sizing when nexthop group shrinks
https://git.kernel.org/netdev/net/c/d3daa33c7af9
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-10-06 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 4:50 Daehyeon Ko
2026-10-02 4:50 ` [PATCH net v2 1/3] ipv4: stop PMTU walk when nexthop group shrinks Daehyeon Ko
2026-10-02 4:50 ` [PATCH net v2 2/3] ipv4: stop exception dump " Daehyeon Ko
2026-10-04 8:02 ` Ido Schimmel
2026-10-02 4:51 ` [PATCH net v2 3/3] ipv4: stop route notification sizing " Daehyeon Ko
2026-10-04 8:20 ` Ido Schimmel
2026-10-06 23:30 ` 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=179132941041.2826662.12574878292005935947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=4ncienth@gmail.com \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=deliran@verdict.gg \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roopa@nvidia.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®