From: patchwork-bot+netdevbpf@kernel.org
To: Yuyang Huang <sigefriedhyy@gmail.com>
Cc: davem@davemloft.net, carges@cloudflare.com,
daniel.zahka@gmail.com, dsahern@kernel.org, dw@davidwei.uk,
dimitri.daskalakis1@gmail.com, donald.hunter@gmail.com,
edumazet@google.com, idosch@nvidia.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, horms@kernel.org,
sdf@fomichev.me, willemb@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v6 00/10] ipv6: report why a route was deleted in RTM_DELROUTE
Date: Thu, 13 Aug 2026 10:51:19 +0000 [thread overview]
Message-ID: <178661827995.2370447.9301462762512450819.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260808005642.26901-1-sigefriedhyy@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 8 Aug 2026 09:56:32 +0900 you wrote:
> When the kernel deletes an IPv6 route on its own, the RTM_DELROUTE
> notification does not say why. User space cannot tell a route that
> expired from one the router explicitly withdrew, yet the two call for
> different reactions: an expired RA route means the router failed to
> refresh it in time, which points at a misconfigured or unreliable
> router and may warrant action such as disabling IPv6 on that network,
> while a zero-lifetime withdrawal is normal, RFC-compliant operation.
>
> [...]
Here is the summary with links:
- [net-next,v6,01/10] ipv6: add ip6_del_rt_reason()
https://git.kernel.org/netdev/net-next/c/cc17e386f8a5
- [net-next,v6,02/10] ipv6: propagate the route deletion reason to fib6_del_route()
https://git.kernel.org/netdev/net-next/c/352c6732ffb2
- [net-next,v6,03/10] ipv6: record the reason for kernel-initiated route deletions
https://git.kernel.org/netdev/net-next/c/e8636445b771
- [net-next,v6,04/10] ipv6: add a deletion reason argument to rt6_fill_node()
https://git.kernel.org/netdev/net-next/c/b0215102356b
- [net-next,v6,05/10] ipv6: expose the route deletion reason in RTM_DELROUTE
https://git.kernel.org/netdev/net-next/c/1e6a83af5914
- [net-next,v6,06/10] ipv6: add inet6_rt_del_notify()
https://git.kernel.org/netdev/net-next/c/09f19ce3de67
- [net-next,v6,07/10] netlink: specs: rt-route: add route notifications
https://git.kernel.org/netdev/net-next/c/bf517422fb26
- [net-next,v6,08/10] netlink: specs: rt-route: split out the request attribute list
https://git.kernel.org/netdev/net-next/c/8621a7ed80f0
- [net-next,v6,09/10] netlink: specs: rt-route: add the route deletion reason
https://git.kernel.org/netdev/net-next/c/b13ba4e82bfd
- [net-next,v6,10/10] selftests: net: verify RTA_DEL_REASON on route deletion
https://git.kernel.org/netdev/net-next/c/046d88326506
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-13 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 0:56 [PATCH net-next v6 00/10] ipv6: report why a route was deleted in RTM_DELROUTE Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 01/10] ipv6: add ip6_del_rt_reason() Yuyang Huang
2026-08-09 8:50 ` Ido Schimmel
2026-08-09 12:30 ` Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 02/10] ipv6: propagate the route deletion reason to fib6_del_route() Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 03/10] ipv6: record the reason for kernel-initiated route deletions Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 04/10] ipv6: add a deletion reason argument to rt6_fill_node() Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 05/10] ipv6: expose the route deletion reason in RTM_DELROUTE Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 06/10] ipv6: add inet6_rt_del_notify() Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 07/10] netlink: specs: rt-route: add route notifications Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 08/10] netlink: specs: rt-route: split out the request attribute list Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 09/10] netlink: specs: rt-route: add the route deletion reason Yuyang Huang
2026-08-08 0:56 ` [PATCH net-next v6 10/10] selftests: net: verify RTA_DEL_REASON on route deletion Yuyang Huang
2026-08-13 10:51 ` 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=178661827995.2370447.9301462762512450819.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=carges@cloudflare.com \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=sigefriedhyy@gmail.com \
--cc=willemb@google.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 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.