netdev - Re: [PATCH net-next v3 00/12] vxlan metadata device vnifiltering support

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: <164612461276.12731.12133825618202154636.git-patchwork-notify@kernel.org>
Date:   Tue, 01 Mar 2022 08:50:12 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Roopa Prabhu <roopa@...dia.com>
Cc:     davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
        stephen@...workplumber.org, nikolay@...ulusnetworks.com,
        idosch@...dia.com, dsahern@...il.com, bpoirier@...dia.com
Subject: Re: [PATCH net-next v3 00/12] vxlan metadata device vnifiltering support

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:

On Tue, 1 Mar 2022 05:04:27 +0000 you wrote:
> This series adds vnifiltering support to vxlan collect metadata device.
> 
> Motivation:
> You can only use a single vxlan collect metadata device for a given
> vxlan udp port in the system today. The vxlan collect metadata device
> terminates all received vxlan packets. As shown in the below diagram,
> there are use-cases where you need to support multiple such vxlan devices in
> independent bridge domains. Each vxlan device must terminate the vni's
> it is configured for.
> Example usecase: In a service provider network a service provider
> typically supports multiple bridge domains with overlapping vlans.
> One bridge domain per customer. Vlans in each bridge domain are
> mapped to globally unique vxlan ranges assigned to each customer.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,01/12] vxlan: move to its own directory
    https://git.kernel.org/netdev/net-next/c/6765393614ea
  - [net-next,v3,02/12] vxlan_core: fix build warnings in vxlan_xmit_one
    https://git.kernel.org/netdev/net-next/c/fba55a66e8ec
  - [net-next,v3,03/12] vxlan_core: move common declarations to private header file
    https://git.kernel.org/netdev/net-next/c/76fc217d7fb1
  - [net-next,v3,04/12] vxlan_core: move some fdb helpers to non-static
    https://git.kernel.org/netdev/net-next/c/c63053e0cb5a
  - [net-next,v3,05/12] vxlan_core: make multicast helper take rip and ifindex explicitly
    https://git.kernel.org/netdev/net-next/c/a9508d121a0e
  - [net-next,v3,06/12] vxlan_core: add helper vxlan_vni_in_use
    https://git.kernel.org/netdev/net-next/c/efe0f94b333b
  - [net-next,v3,07/12] rtnetlink: add new rtm tunnel api for tunnel id filtering
    https://git.kernel.org/netdev/net-next/c/7b8135f4df98
  - [net-next,v3,08/12] vxlan_multicast: Move multicast helpers to a separate file
    https://git.kernel.org/netdev/net-next/c/a498c5953a9c
  - [net-next,v3,09/12] vxlan: vni filtering support on collect metadata device
    https://git.kernel.org/netdev/net-next/c/f9c4bb0b245c
  - [net-next,v3,10/12] selftests: add new tests for vxlan vnifiltering
    https://git.kernel.org/netdev/net-next/c/3edf5f66c12a
  - [net-next,v3,11/12] drivers: vxlan: vnifilter: per vni stats
    https://git.kernel.org/netdev/net-next/c/4095e0e1328a
  - [net-next,v3,12/12] drivers: vxlan: vnifilter: add support for stats dumping
    https://git.kernel.org/netdev/net-next/c/445b2f36bb4e

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