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: 
 <174285483355.3937.1490840167565257776.git-patchwork-notify@kernel.org>
Date: Mon, 24 Mar 2025 22:20:33 +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, horms@...nel.org, andrew+netdev@...n.ch,
 netdev@...r.kernel.org, idosch@...dia.com, amcohen@...dia.com,
 mlxsw@...dia.com
Subject: Re: [PATCH net-next 0/6] mlxsw: Add VXLAN to the same hardware domain as
 physical bridge ports

Hello:

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

On Mon, 17 Mar 2025 18:37:25 +0100 you wrote:
> Amit Cohen writes:
> 
> Packets which are trapped to CPU for forwarding in software data path
> are handled according to driver marking of skb->offload_{,l3}_fwd_mark.
> Packets which are marked as L2-forwarded in hardware, will not be flooded
> by the bridge to bridge ports which are in the same hardware domain as the
> ingress port.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] mlxsw: Trap ARP packets at layer 2 instead of layer 3
    https://git.kernel.org/netdev/net-next/c/6d627a29aab8
  - [net-next,2/6] mlxsw: spectrum: Call mlxsw_sp_bridge_vxlan_{join, leave}() for VLAN-aware bridge
    https://git.kernel.org/netdev/net-next/c/a13fc7ebd994
  - [net-next,3/6] mlxsw: spectrum_switchdev: Add an internal API for VXLAN leave
    https://git.kernel.org/netdev/net-next/c/413e2c069969
  - [net-next,4/6] mlxsw: spectrum_switchdev: Move mlxsw_sp_bridge_vxlan_join()
    https://git.kernel.org/netdev/net-next/c/630e7e20d35f
  - [net-next,5/6] mlxsw: Add VXLAN bridge ports to same hardware domain as physical bridge ports
    https://git.kernel.org/netdev/net-next/c/139ae87714eb
  - [net-next,6/6] selftests: vxlan_bridge: Test flood with unresolved FDB entry
    https://git.kernel.org/netdev/net-next/c/36ed81bcade9

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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ