netdev - RE: Question regarding failure utilizing bonding mode 5 (balance-tlb)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Sep 2013 11:30:40 +0000
From:	"Yuval Mintz" <yuvalmin@...adcom.com>
To:	"Jay Vosburgh" <fubar@...ibm.com>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Ariel Elior" <ariele@...adcom.com>
Subject: RE: Question regarding failure utilizing bonding mode 5
 (balance-tlb)

> > >Again, I think the permanent address is restored only when the bond
> > >releases the slave, which I don't think happens when the slave is unloaded.
> >
> > 	Ah, ok, I was understanding "unloaded" to mean "remove from the
> > bond."  I think you actually mean "set administratively down," e.g., "ip
> > link set dev slave down" or the like.  I don't think mere loss of
> > carrier would trigger the sequence of events, because that won't go
> > through a dev_close / dev_open cycle.
> >
> > 	Doing that (an admin down / up bounce) would, indeed, cause a
> > failover, but the bond will not reprogram the MAC on the slave (it
> > presumes that a fail / recovery will not disrupt the MAC address, which
> > is apparently not true in this instance).
> >
> > 	I'll have to look at the code a bit, but for now can you confirm
> > that what you actually mean is, essentially:
> >
> > 	Given a bond0 with two slaves, eth0 and eth1, in tlb mode, eth0
> > being the active,
> >
> > 	1) "ip link set dev eth0 down" which will fail over to eth1
> > 		(swapping the contents of their dev_addr fields).
> >
> > 	2) "ip link set dev eth0 up" eth0 comes back up, reprograms its
> > 		MAC to the wrong thing (what was in dev_addr).
> >
> > 	3) repeat steps 1 and 2 for eth1
> >
> > 	Is this correct?
> >
> 
> Yes, sorry for the earlier confusion.
> I think in the case described `alb_swap_mac_addr()' will be called,
> replacing eth0 and eth1's dev_addr, causing eth0 to have dev_addr
> which defers from  the bond device's. Once eth0 reloads, it will use
> the different MAC address for configuring FW/HW.

Hi,

Did you by any chance had the time to look at this issue?

Thanks,
Yuval

--
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