netdev - Re: [net-next-2.6 PATCH 3/3] bonding: reread information about speed and duplex when interface goes up

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: <20101006.142831.102541368.davem@davemloft.net>
Date:	Wed, 06 Oct 2010 14:28:31 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ole@....pl
Cc:	fubar@...ibm.com, bonding-devel@...ts.sourceforge.net,
	netdev@...r.kernel.org
Subject: Re: [net-next-2.6 PATCH 3/3] bonding: reread information about
 speed and duplex when interface goes up

From: Krzysztof Piotr Oledzki <ole@....pl>
Date: Thu, 30 Sep 2010 18:19:10 +0200

>>>From 43285224a785e90c7d4cff2be0766ca8df6ddfb9 Mon Sep 17 00:00:00 2001
> From: Krzysztof Piotr Oledzki <ole@....pl>
> Date: Thu, 30 Sep 2010 17:09:02 +0200
> Subject: bonding: reread information about speed and duplex when interface goes up
> 
> When an interface was enslaved when it was down, bonding thinks
> it has speed -1 even after it goes up. This leads into selecting
> a wrong active interface in active/backup mode on mixed 10G/1G or
> 1G/100M environment.
> 
> before:
>  bonding: bond0: link status definitely up for interface eth5, 100 Mbps full duplex.
>  bonding: bond0: link status definitely up for interface eth0, 100 Mbps full duplex.
> 
> after:
>  bonding: bond0: link status definitely up for interface eth5, 10000 Mbps full duplex.
>  bonding: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex.
> 
> Signed-off-by: Krzysztof Piotr Oledzki <ole@....pl>

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