netdev - Re: [PATCH net-next v3 0/2] bonding: fix primary problem for bonding

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] [day] [month] [year] [list]

Message-Id: <20140122.174626.1807653611284621368.davem@davemloft.net>
Date:	Wed, 22 Jan 2014 17:46:26 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	dingtianhong@...wei.com
Cc:	fubar@...ibm.com, vfalico@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 0/2] bonding: fix primary problem for
 bonding

From: Ding Tianhong <dingtianhong@...wei.com>
Date: Sat, 18 Jan 2014 16:28:47 +0800

> If the slave's name changed, and the bond params primary is exist,
> the bond should deal with the situation in two ways:
> 
> 1) If the slave was the primary slave yet, clean the primary slave
>    and reselect active slave.
> 2) If the slave's new name is as same as bond primary, set the slave
>    as primary slave and reselect active slave.
> 
> If the new primary is not matching any slave in the bond, the bond should
> record it to params, clean the primary slave and select a new active slave.
> 
> Update bonding.txt for primary description.

Series 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