netdev - Re: [PATCH net-next v3 00/15] ipmr, ip6mr: Allow MC-routing locally-generated MC packets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <175021087241.3761578.9440566211529797488.git-patchwork-notify@kernel.org>
Date: Wed, 18 Jun 2025 01:41:12 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Petr Machata <petrm@...dia.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, dsahern@...il.com, netdev@...r.kernel.org,
 horms@...nel.org, razor@...ckwall.org, idosch@...dia.com, mlxsw@...dia.com
Subject: Re: [PATCH net-next v3 00/15] ipmr,
 ip6mr: Allow MC-routing locally-generated MC packets

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Tue, 17 Jun 2025 00:44:08 +0200 you wrote:
> Multicast routing is today handled in the input path. Locally generated MC
> packets don't hit the IPMR code. Thus if a VXLAN remote address is
> multicast, the driver needs to set an OIF during route lookup. In practice
> that means that MC routing configuration needs to be kept in sync with the
> VXLAN FDB and MDB. Ideally, the VXLAN packets would be routed by the MC
> routing code instead.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,01/15] net: ipv4: Add a flags argument to iptunnel_xmit(), udp_tunnel_xmit_skb()
    https://git.kernel.org/netdev/net-next/c/e3411e326fa4
  - [net-next,v3,02/15] net: ipv4: ipmr: ipmr_queue_xmit(): Drop local variable `dev'
    https://git.kernel.org/netdev/net-next/c/3b7bc938e0ad
  - [net-next,v3,03/15] net: ipv4: ipmr: Split ipmr_queue_xmit() in two
    https://git.kernel.org/netdev/net-next/c/b2e653bcff0f
  - [net-next,v3,04/15] net: ipv4: Add ip_mr_output()
    https://git.kernel.org/netdev/net-next/c/35bec72a24ac
  - [net-next,v3,05/15] net: ipv6: Make udp_tunnel6_xmit_skb() void
    https://git.kernel.org/netdev/net-next/c/6a7d88ca15f7
  - [net-next,v3,06/15] net: ipv6: Add a flags argument to ip6tunnel_xmit(), udp_tunnel6_xmit_skb()
    https://git.kernel.org/netdev/net-next/c/f78c75d84fe8
  - [net-next,v3,07/15] net: ipv6: ip6mr: Fix in/out netdev to pass to the FORWARD chain
    https://git.kernel.org/netdev/net-next/c/3365afd3abda
  - [net-next,v3,08/15] net: ipv6: ip6mr: Make ip6mr_forward2() void
    https://git.kernel.org/netdev/net-next/c/094f39d5e84d
  - [net-next,v3,09/15] net: ipv6: ip6mr: Split ip6mr_forward2() in two
    https://git.kernel.org/netdev/net-next/c/1b02f4475d29
  - [net-next,v3,10/15] net: ipv6: Add ip6_mr_output()
    https://git.kernel.org/netdev/net-next/c/96e8f5a9fe2d
  - [net-next,v3,11/15] vxlan: Support MC routing in the underlay
    https://git.kernel.org/netdev/net-next/c/f8337efa4ff5
  - [net-next,v3,12/15] selftests: forwarding: lib: Move smcrouted helpers here
    https://git.kernel.org/netdev/net-next/c/2a719b7bacc7
  - [net-next,v3,13/15] selftests: net: lib: Add ip_link_has_flag()
    https://git.kernel.org/netdev/net-next/c/4baa1d3a5080
  - [net-next,v3,14/15] selftests: forwarding: adf_mcd_start(): Allow configuring custom interfaces
    https://git.kernel.org/netdev/net-next/c/237f84a6d24a
  - [net-next,v3,15/15] selftests: forwarding: Add a test for verifying VXLAN MC underlay
    https://git.kernel.org/netdev/net-next/c/e3180379e2df

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html