From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
olteanv@gmail.com, kurt@linutronix.de, hauke@hauke-m.de,
woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
sean.wang@mediatek.com, Landen.Chao@mediatek.com,
dqfext@gmail.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, linus.walleij@linaro.org,
alsi@bang-olufsen.dk, george.mccollister@gmail.com
Subject: Re: [PATCH v2 net-next 00/10] DSA FDB isolation
Date: Sun, 27 Feb 2022 11:10:14 +0000 [thread overview]
Message-ID: <164596021490.1414.6291195308160851459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220225092225.594851-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.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
prev parent reply other threads:[~2022-02-27 11:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 9:22 [PATCH v2 net-next 00/10] DSA FDB isolation Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 01/10] net: dsa: tag_8021q: replace the SVL bridging with VLAN-unaware IVL bridging Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 02/10] net: dsa: tag_8021q: add support for imprecise RX based on the VBID Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 03/10] docs: net: dsa: sja1105: document limitations of tc-flower rule VLAN awareness Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 04/10] net: dsa: felix: delete workarounds present due to SVL tag_8021q bridging Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 05/10] net: dsa: tag_8021q: merge RX and TX VLANs Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 06/10] net: dsa: tag_8021q: rename dsa_8021q_bridge_tx_fwd_offload_vid Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 07/10] net: dsa: request drivers to perform FDB isolation Vladimir Oltean
2022-04-26 15:01 ` Hans Schultz
2022-04-26 16:14 ` Andrew Lunn
2022-04-26 23:17 ` Vladimir Oltean
2022-04-27 8:38 ` Hans Schultz
2022-04-27 10:32 ` Vladimir Oltean
2022-04-27 11:06 ` Hans Schultz
2022-04-27 6:45 ` Hans Schultz
2022-02-25 9:22 ` [PATCH v2 net-next 08/10] net: dsa: pass extack to .port_bridge_join driver methods Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 09/10] net: dsa: sja1105: enforce FDB isolation Vladimir Oltean
2022-02-25 9:22 ` [PATCH v2 net-next 10/10] net: mscc: ocelot: enforce FDB isolation when VLAN-unaware Vladimir Oltean
2022-02-27 11:10 ` 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=164596021490.1414.6291195308160851459.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Landen.Chao@mediatek.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linus.walleij@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=woojung.huh@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.