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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 03 Mar 2022 14:20:12 +0000
To:     Vladimir Oltean <>
Subject: Re: [PATCH net-next 00/10] DSA unicast filtering


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

On Wed,  2 Mar 2022 21:14:07 +0200 you wrote:
> This series doesn't attempt anything extremely brave, it just changes
> the way in which standalone ports which support FDB isolation work.
> Up until now, DSA has recommended that switch drivers configure
> standalone ports in a separate VID/FID with learning disabled, and with
> the CPU port as the only destination, reached trivially via flooding.
> That works, except that standalone ports will deliver all packets to the
> CPU. We can leverage the hardware FDB as a MAC DA filter, and disable
> flooding towards the CPU port, to force the dropping of packets with
> unknown MAC DA.
> [...]

Here is the summary with links:
  - [net-next,01/10] net: dsa: remove workarounds for changing master promisc/allmulti only while up
  - [net-next,02/10] net: dsa: rename the host FDB and MDB methods to contain the "bridge" namespace
  - [net-next,03/10] net: dsa: install secondary unicast and multicast addresses as host FDB/MDB
  - [net-next,04/10] net: dsa: install the primary unicast MAC address as standalone port host FDB
  - [net-next,05/10] net: dsa: manage flooding on the CPU ports
  - [net-next,06/10] net: dsa: felix: migrate host FDB and MDB entries when changing tag proto
  - [net-next,07/10] net: dsa: felix: migrate flood settings from NPI to tag_8021q CPU port
  - [net-next,08/10] net: dsa: felix: start off with flooding disabled on the CPU port
  - [net-next,09/10] net: dsa: felix: stop clearing CPU flooding in felix_setup_tag_8021q
  - [net-next,10/10] net: mscc: ocelot: accept configuring bridge port flags on the NPI port

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists