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,
willemdebruijn.kernel@gmail.com, horms@kernel.org
Subject: Re: [PATCH net-next] ipv6: udp: Use ip6_sk_redirect() for tunnel sockets
Date: Tue, 08 Sep 2026 12:50:06 +0000 [thread overview]
Message-ID: <178887180639.3511527.1640935140177520250.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260907101358.596953-1-idosch@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 7 Sep 2026 13:13:58 +0300 you wrote:
> After commit cd51b74bdd0b ("ipv6: Fix redirect exception creation for
> UDP/RAW sockets") the two redirect calls are now equivalent and there is
> no need to specifically call ip6_redirect() for tunnel sockets. Simplify
> and call ip6_sk_redirect() for both tunnel sockets and regular sockets.
>
> Note that for ICMPv6 Redirect Message packets the VRF driver does not
> reset skb->dev to the VRF device, so skb->dev->ifindex is equivalent to
> inet6_iif(skb), even when the packet was received from a VRF port.
>
> [...]
Here is the summary with links:
- [net-next] ipv6: udp: Use ip6_sk_redirect() for tunnel sockets
https://git.kernel.org/netdev/net-next/c/4596be8a15db
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-08 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 10:13 [PATCH net-next] ipv6: udp: Use ip6_sk_redirect() for tunnel sockets Ido Schimmel
2026-09-07 13:06 ` Eric Dumazet
2026-09-08 12: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=178887180639.3511527.1640935140177520250.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.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