| 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
| ||
|
Date: Fri, 8 May 2009 16:12:04 -0700 From: Stephen Hemminger <shemminger@...tta.com> To: David Miller <davem@...emloft.net> Cc: jpirko@...hat.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, jgarzik@...ox.com, shemminger@...ux-foundation.org, bridge@...ts.linux-foundation.org, fubar@...ibm.com, bonding-devel@...ts.sourceforge.net, kaber@...sh.net, mschmidt@...hat.com, dada1@...mosbay.com, ivecera@...hat.com Subject: Re: [PATCH] net: introduce a list of device addresses dev_addr_list (v6) On Fri, 08 May 2009 16:00:08 -0700 (PDT) David Miller <davem@...emloft.net> wrote: > From: Stephen Hemminger <shemminger@...tta.com> > Date: Fri, 8 May 2009 15:38:42 -0700 > > > Not sure if this is such a good idea since the purpose of this was to fix > > a bonding/bridging interaction, but it breaks STP on bridging. > > Thanks for not paying attention... :-/ > > The Intel folks want to have an address list functionality so > they can public MAC addresses meant for FCOE and other purposes. > > So even if the bonding bits bomb, we still need this. But the other infrastructure may have same issues (netfilter, etc). Just seems like it would be either to have multiple network devices so that upper layers could disambiguate easier. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists