netdev - Re: [PATCH net 1/7] bridge: Fix the way finding the old local fdb entry in br_fdb

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131203085035.6a11b1de@nehalam.linuxnetplumber.net>
Date:	Tue, 3 Dec 2013 08:50:35 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Toshiaki Makita <makita.toshiaki@....ntt.co.jp>
Cc:	"David S . Miller" <davem@...emloft.net>,
	Vlad Yasevich <vyasevic@...hat.com>, netdev@...r.kernel.org
Subject: Re: [PATCH net 1/7] bridge: Fix the way finding the old local fdb
 entry in br_fdb_changeaddr

On Tue, 03 Dec 2013 21:55:26 +0900
Toshiaki Makita <makita.toshiaki@....ntt.co.jp> wrote:

> Another approach I can conceive is:
> - Make fdb entries be able to be differentiated from those user added
>   by introducing a flag in struct net_bridge_fdb_entry. 

Yes, this makes more sense; and it would be useful for administration display commands.
--
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