From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, horms@kernel.org,
paul@paul-moore.com, dsahern@kernel.org, petrm@nvidia.com,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/8] ipv4: icmp: Fix source IP derivation in presence of VRFs
Date: Thu, 11 Sep 2025 10:40:17 +0000 [thread overview]
Message-ID: <175758721750.2121362.2938390570083622671.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250908073238.119240-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 8 Sep 2025 10:32:30 +0300 you wrote:
> Align IPv4 with IPv6 and in the presence of VRFs generate ICMP error
> messages with a source IP that is derived from the receiving interface
> and not from its VRF master. This is especially important when the error
> messages are "Time Exceeded" messages as it means that utilities like
> traceroute will show an incorrect packet path.
>
> Patches #1-#2 are preparations.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] ipv4: cipso: Simplify IP options handling in cipso_v4_error()
https://git.kernel.org/netdev/net-next/c/cda276bcb9a5
- [net-next,v2,2/8] ipv4: icmp: Pass IPv4 control block structure as an argument to __icmp_send()
https://git.kernel.org/netdev/net-next/c/0d3c4a441686
- [net-next,v2,3/8] ipv4: icmp: Fix source IP derivation in presence of VRFs
https://git.kernel.org/netdev/net-next/c/4a8c416602d9
- [net-next,v2,4/8] selftests: traceroute: Return correct value on failure
https://git.kernel.org/netdev/net-next/c/c068ba9d3ded
- [net-next,v2,5/8] selftests: traceroute: Use require_command()
https://git.kernel.org/netdev/net-next/c/47efbac9b768
- [net-next,v2,6/8] selftests: traceroute: Reword comment
https://git.kernel.org/netdev/net-next/c/5c9c78224fc3
- [net-next,v2,7/8] selftests: traceroute: Test traceroute with different source IPs
https://git.kernel.org/netdev/net-next/c/2e6428100b16
- [net-next,v2,8/8] selftests: traceroute: Add VRF tests
https://git.kernel.org/netdev/net-next/c/f7240999deb4
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:[~2025-09-11 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 7:32 [PATCH net-next v2 0/8] ipv4: icmp: Fix source IP derivation in presence of VRFs Ido Schimmel
2025-09-08 7:32 ` [PATCH net-next v2 1/8] ipv4: cipso: Simplify IP options handling in cipso_v4_error() Ido Schimmel
2025-09-08 7:51 ` Eric Dumazet
2025-09-08 7:32 ` [PATCH net-next v2 2/8] ipv4: icmp: Pass IPv4 control block structure as an argument to __icmp_send() Ido Schimmel
2025-09-08 7:55 ` Eric Dumazet
2025-09-08 7:32 ` [PATCH net-next v2 3/8] ipv4: icmp: Fix source IP derivation in presence of VRFs Ido Schimmel
2025-09-08 7:32 ` [PATCH net-next v2 4/8] selftests: traceroute: Return correct value on failure Ido Schimmel
2025-09-08 7:32 ` [PATCH net-next v2 5/8] selftests: traceroute: Use require_command() Ido Schimmel
2025-09-08 7:32 ` [PATCH net-next v2 6/8] selftests: traceroute: Reword comment Ido Schimmel
2025-09-08 7:32 ` [PATCH net-next v2 7/8] selftests: traceroute: Test traceroute with different source IPs Ido Schimmel
2025-09-08 7:32 ` [PATCH net-next v2 8/8] selftests: traceroute: Add VRF tests Ido Schimmel
2025-09-11 10:40 ` 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=175758721750.2121362.2938390570083622671.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=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=petrm@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