netdev - Re: [iproute2] bridge: link: allow filtering on bridge name

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: <CUBX0CEWRC2S.1PMUD29FODN5J@syracuse>
Date: Wed, 26 Jul 2023 09:11:22 +0200
From: "Nicolas Escande" <nico.escande@...il.com>
To: "Stephen Hemminger" <stephen@...workplumber.org>
Cc: <netdev@...r.kernel.org>
Subject: Re: [iproute2] bridge: link: allow filtering on bridge name

On Wed Jul 26, 2023 at 4:16 AM CEST, Stephen Hemminger wrote:
>
> Leave it there for now. Only Linux uses the term master.
> FreeBSD and other use the term adding interface to bridge (addm)
>
> IEEE uses the term relay mostly.
>
> You won't find the terms master/slave in any current spec.
>
> > On another note, there is a slight indentation problem in the new if in
> > print_linkinfo(), if that can be corrected when the patch gets picked up that
> > would be perfect, otherwise I can send a v2.
>
> Send a v2, that would be easier

OK, I'll get right on it.