netdev - Re: [PATCH net-next] bridge: del external_learned fdbs from device on flush or ageout

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: <20150615.170924.2212463704435329039.davem@davemloft.net>
Date:	Mon, 15 Jun 2015 17:09:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sfeldma@...il.com
Cc:	netdev@...r.kernel.org, jiri@...nulli.us,
	roopa@...ulusnetworks.com, john.r.fastabend@...el.com,
	andrew@...n.ch, f.fainelli@...il.com, linux@...ck-us.net,
	stephen@...workplumber.org
Subject: Re: [PATCH net-next] bridge: del external_learned fdbs from device
 on flush or ageout

From: sfeldma@...il.com
Date: Sun, 14 Jun 2015 11:33:11 -0700

> From: Scott Feldman <sfeldma@...il.com>
> 
> We need to delete from offload the device externally learnded fdbs when any
> one of these events happen:
> 
> 1) Bridge ages out fdb.  (When bridge is doing ageing vs. device doing
> ageing.  If device is doing ageing, it would send SWITCHDEV_FDB_DEL
> directly).
> 
> 2) STP state change flushes fdbs on port.
> 
> 3) User uses sysfs interface to flush fdbs from bridge or bridge port:
> 
> 	echo 1 >/sys/class/net/BR_DEV/bridge/flush
> 	echo 1 >/sys/class/net/BR_PORT/brport/flush
> 
> 4) Offload driver send event SWITCHDEV_FDB_DEL to delete fdb entry.
> 
> For rocker, we can now get called to delete fdb entry in wait and nowait
> contexts, so set NOWAIT flag when deleting fdb entry.
> 
> Signed-off-by: Scott Feldman <sfeldma@...il.com>

Applied, thanks Scott.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html