netdev - Re: [patch net-next v2 2/2] mlxsw: spectrum: remove FDB entry in case we get unknown object notification

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: <20160109.210708.1566592679545936608.davem@davemloft.net>
Date:	Sat, 09 Jan 2016 21:07:08 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jiri@...nulli.us
Cc:	netdev@...r.kernel.org, idosch@...lanox.com, eladr@...lanox.com,
	yotamg@...lanox.com, ogerlitz@...lanox.com
Subject: Re: [patch net-next v2 2/2] mlxsw: spectrum: remove FDB entry in
 case we get unknown object notification

From: Jiri Pirko <jiri@...nulli.us>
Date: Thu,  7 Jan 2016 11:50:30 +0100

> From: Jiri Pirko <jiri@...lanox.com>
> 
> It may happen that we get notification for FDB entry for object (port,
> lag, vport), which does not exist. Currently we ignore that, which only
> causes this being re-sent in next notification. The entry will never
> disappear. So get rid of it by simply removing it using SFD register.
> 
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>
> Reviewed-by: Ido Schimmel <idosch@...lanox.com>
> ---
> v1->v2:
> - fixing impossible mlxsw_sp_port null dereference

Applied.