netdev - Re: [PATCH v3] bonding: "primary_reselect" with "failure" is not working properly

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: <20150708.160634.2087986100168064781.davem@davemloft.net>
Date:	Wed, 08 Jul 2015 16:06:34 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ranamazharp@...il.com
Cc:	j.vosburgh@...il.com, vfalico@...il.com, gospo@...ulusnetworks.com,
	mazhar.rana@...eroam.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, sanket.shah@...eroam.com
Subject: Re: [PATCH v3] bonding: "primary_reselect" with "failure" is not
 working properly

From: Mazhar Rana <ranamazharp@...il.com>
Date: Tue,  7 Jul 2015 15:04:50 +0530

> From: Mazhar Rana <mazhar.rana@...eroam.com>
> 
> When "primary_reselect" is set to "failure", primary interface should
> not become active until current active slave is down. But if we set first
> member of bond device as a "primary" interface and "primary_reselect"
> is set to "failure" then whenever primary interface's link get back(up)
> it become active slave even if current active slave is still up.
> 
> With this patch, "bond_find_best_slave" will not traverse members if
> primary interface is not candidate for failover/reselection and current
> active slave is still up.
> 
> Signed-off-by: Mazhar Rana <mazhar.rana@...eroam.com>
> Signed-off-by: Jay Vosburgh <j.vosburgh@...il.com>

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