From: patchwork-bot+netdevbpf@kernel.org
To: Sagarika Sharma <sharmasagarika@google.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] ipv6: fix ECMP route failover on carrier loss
Date: Sat, 02 May 2026 01:50:09 +0000 [thread overview]
Message-ID: <177768660905.3689119.5102123801449238514.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260430200909.527827-1-sharmasagarika@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 30 Apr 2026 20:08:59 +0000 you wrote:
> This patchset resolves an issue where established IPv6 connections are
> unable to transition to alternative ECMP nexthops upon carrier loss.
>
> Unlike IPv4, the IPv6 routing subsystem does not actively invalidate
> cached destinations during a NETDEV_CHANGE event. Sockets persist
> with dead routes, leading to stalled traffic or connection drops.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] ipv6: update route serial number on NETDEV_CHANGE
https://git.kernel.org/netdev/net/c/4bc852006b62
- [net,v2,2/2] selftest: net: Add test for TCP flow failover with ECMP routes.
https://git.kernel.org/netdev/net/c/d1ae37dc6881
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-05-02 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 20:08 [PATCH net v2 0/2] ipv6: fix ECMP route failover on carrier loss Sagarika Sharma
2026-04-30 20:09 ` [PATCH net v2 1/2] ipv6: update route serial number on NETDEV_CHANGE Sagarika Sharma
2026-04-30 20:09 ` [PATCH net v2 2/2] selftest: net: Add test for TCP flow failover with ECMP routes Sagarika Sharma
2026-05-02 1: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=177768660905.3689119.5102123801449238514.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharmasagarika@google.com \
--cc=shuah@kernel.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