| 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
| ||
|
Message-ID: <20110216143923.GB5727@psychotron.brq.redhat.com> Date: Wed, 16 Feb 2011 15:39:24 +0100 From: Jiri Pirko <jpirko@...hat.com> To: Stephen Hemminger <shemminger@...tta.com> Cc: netdev@...r.kernel.org, davem@...emloft.net, shemminger@...ux-foundation.org, kaber@...sh.net, fubar@...ibm.com, eric.dumazet@...il.com, nicolas.2p.debian@...il.com Subject: Re: [patch net-next-2.6 1/4] rtnetlink: implement setting of master device Wed, Feb 16, 2011 at 02:18:44PM CET, shemminger@...tta.com wrote: >On Sun, 13 Feb 2011 20:31:06 +0100 >Jiri Pirko <jpirko@...hat.com> wrote: > >> This patch allows userspace to enslave/release slave devices via netlink >> interface using IFLA_MASTER. This introduces generic way to add/remove >> underling devices. >> >> Signed-off-by: Jiri Pirko <jpirko@...hat.com> > >But, setting master means something different for each type of device? Why isn't correct to use master also for bridge? It had no meaning there. >What happens if you move eth0 from br0 to bond0? you mean by: ip link set eth0 master br0 ip link set eth0 master bond0 It's first removed from bridge, then added into bond. No problem here. > >The name "master" is only used in the bonding spec. It is not used in >description of bridges in the 802.1 spec. There are also some companies >that have very "politically correct" HR departments that think that any >reference to master or slave is racist. > > -- 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
Powered by blists - more mailing lists