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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231215115843.GH6288@kernel.org>
Date: Fri, 15 Dec 2023 11:58:43 +0000
From: Simon Horman <horms@...nel.org>
To: Ioana Ciornei <ioana.ciornei@....com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
	pabeni@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 8/8] dpaa2-switch: cleanup the egress flood
 of an unused FDB

On Wed, Dec 13, 2023 at 02:14:11PM +0200, Ioana Ciornei wrote:
> In case a DPAA2 switch interface joins a bridge, the FDB used on the
> port will be changed to the one associated with the bridge. What this
> means exactly is that any VLAN installed on the port will need to be
> removed and then installed back so that it points to the new FDB.
> 
> Once this is done, the previous FDB will become unused (no VLAN to
> point to it). Even though no traffic will reach this FDB, it's best to
> just cleanup the state of the FDB by zeroing its egress flood domain.
> 
> Signed-off-by: Ioana Ciornei <ioana.ciornei@....com>

Reviewed-by: Simon Horman <horms@...nel.org>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ