netdev - Re: [PATCH v2 net-next 00/10] DSA FDB isolation

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <164596021490.1414.6291195308160851459.git-patchwork-notify@kernel.org>
Date:   Sun, 27 Feb 2022 11:10:14 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Vladimir Oltean <vladimir.oltean@....com>
Cc:     netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
        f.fainelli@...il.com, andrew@...n.ch, vivien.didelot@...il.com,
        olteanv@...il.com, kurt@...utronix.de, hauke@...ke-m.de,
        woojung.huh@...rochip.com, UNGLinuxDriver@...rochip.com,
        sean.wang@...iatek.com, Landen.Chao@...iatek.com, dqfext@...il.com,
        claudiu.manoil@....com, alexandre.belloni@...tlin.com,
        linus.walleij@...aro.org, alsi@...g-olufsen.dk,
        george.mccollister@...il.com
Subject: Re: [PATCH v2 net-next 00/10] DSA FDB isolation

Hello:

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

On Fri, 25 Feb 2022 11:22:15 +0200 you wrote:
> There are use cases which need FDB isolation between standalone ports
> and bridged ports, as well as isolation between ports of different
> bridges. Most of these use cases are a result of the fact that packets
> can now be partially forwarded by the software bridge, so one port might
> need to send a packet to the CPU but its FDB lookup will see that it can
> forward it directly to a bridge port where that packet was autonomously
> learned. So the source port will attempt to shortcircuit the CPU and
> forward autonomously, which it can't due to the forwarding isolation we
> have in place. So we will have packet drops instead of proper operation.
> 
> [...]

Here is the summary with links:
  - [v2,net-next,01/10] net: dsa: tag_8021q: replace the SVL bridging with VLAN-unaware IVL bridging
    https://git.kernel.org/netdev/net-next/c/91495f21fcec
  - [v2,net-next,02/10] net: dsa: tag_8021q: add support for imprecise RX based on the VBID
    https://git.kernel.org/netdev/net-next/c/d7f9787a763f
  - [v2,net-next,03/10] docs: net: dsa: sja1105: document limitations of tc-flower rule VLAN awareness
    https://git.kernel.org/netdev/net-next/c/d27656d02d85
  - [v2,net-next,04/10] net: dsa: felix: delete workarounds present due to SVL tag_8021q bridging
    https://git.kernel.org/netdev/net-next/c/08f44db3abe6
  - [v2,net-next,05/10] net: dsa: tag_8021q: merge RX and TX VLANs
    https://git.kernel.org/netdev/net-next/c/04b67e18ce5b
  - [v2,net-next,06/10] net: dsa: tag_8021q: rename dsa_8021q_bridge_tx_fwd_offload_vid
    https://git.kernel.org/netdev/net-next/c/b6362bdf750b
  - [v2,net-next,07/10] net: dsa: request drivers to perform FDB isolation
    https://git.kernel.org/netdev/net-next/c/c26933639b54
  - [v2,net-next,08/10] net: dsa: pass extack to .port_bridge_join driver methods
    https://git.kernel.org/netdev/net-next/c/06b9cce42634
  - [v2,net-next,09/10] net: dsa: sja1105: enforce FDB isolation
    https://git.kernel.org/netdev/net-next/c/219827ef92f8
  - [v2,net-next,10/10] net: mscc: ocelot: enforce FDB isolation when VLAN-unaware
    https://git.kernel.org/netdev/net-next/c/54c319846086

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