netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v3] bonding: Inactive slaves should keep inactive flag's value
@ 2014-04-02  3:01 Zheng Li
  2014-04-03  2:16 ` zheng.li
  2014-04-04 14:04 ` David Miller
  0 siblings, 2 replies; 3+ messages in thread
From: Zheng Li @ 2014-04-02  3:01 UTC (permalink / raw)
  To: netdev, j.vosburgh, fubar, andy, vfalico
  Cc: linux-kernel, davem, joe.jin, zheng.x.li

bond_open is not setting the inactive flag correctly for some modes (alb and
tlb), resulting in error behavior if the bond has been administratively set
down and then back up. This effect should not occur when slaves are added while
the bond is up; it's something that only happens after a down/up bounce of the
bond.

For example, in bond tlb or alb mode, domu send some ARP request which go out
from dom0 bond's active slave, then the ARP broadcast request packets go back to
inactive slave from switch, because the inactive slave's inactive flag is zero,
kernel will receive the packets and pass them to bridge that cause dom0's bridge
map domu's MAC address to port of bond, bridge should map domu's MAC to port of
vif.

Signed-off-by: Zheng Li <zheng.x.li@oracle.com>
Signed-off-by: Jay Vosburgh <j.vosburgh@gmail.com>
---
 drivers/net/bonding/bond_main.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index e5628fc..b42758f 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -3058,7 +3058,7 @@ static int bond_open(struct net_device *bond_dev)
 	if (bond_has_slaves(bond)) {
 		read_lock(&bond->curr_slave_lock);
 		bond_for_each_slave(bond, slave, iter) {
-			if ((bond->params.mode == BOND_MODE_ACTIVEBACKUP)
+			if (USES_PRIMARY(bond->params.mode)
 				&& (slave != bond->curr_active_slave)) {
 				bond_set_slave_inactive_flags(slave,
 							      BOND_SLAVE_NOTIFY_NOW);
-- 
1.7.6.5

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v3] bonding: Inactive slaves should keep inactive flag's value
  2014-04-02  3:01 [PATCH v3] bonding: Inactive slaves should keep inactive flag's value Zheng Li
@ 2014-04-03  2:16 ` zheng.li
  2014-04-04 14:04 ` David Miller
  1 sibling, 0 replies; 3+ messages in thread
From: zheng.li @ 2014-04-03  2:16 UTC (permalink / raw)
  To: j.vosburgh
  Cc: Zheng Li, netdev, fubar, andy, vfalico, linux-kernel, davem,
	joe.jin

Hi Jay,
How do you think about the new patch used USES_PRIMARY, can it be merged
to upstream?

Thanks,
Zheng Li


于 2014年04月02日 11:01, Zheng Li 写道:
> bond_open is not setting the inactive flag correctly for some modes (alb and
> tlb), resulting in error behavior if the bond has been administratively set
> down and then back up. This effect should not occur when slaves are added while
> the bond is up; it's something that only happens after a down/up bounce of the
> bond.
> 
> For example, in bond tlb or alb mode, domu send some ARP request which go out
> from dom0 bond's active slave, then the ARP broadcast request packets go back to
> inactive slave from switch, because the inactive slave's inactive flag is zero,
> kernel will receive the packets and pass them to bridge that cause dom0's bridge
> map domu's MAC address to port of bond, bridge should map domu's MAC to port of
> vif.
> 
> Signed-off-by: Zheng Li <zheng.x.li@oracle.com>
> Signed-off-by: Jay Vosburgh <j.vosburgh@gmail.com>
> ---
>  drivers/net/bonding/bond_main.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> index e5628fc..b42758f 100644
> --- a/drivers/net/bonding/bond_main.c
> +++ b/drivers/net/bonding/bond_main.c
> @@ -3058,7 +3058,7 @@ static int bond_open(struct net_device *bond_dev)
>  	if (bond_has_slaves(bond)) {
>  		read_lock(&bond->curr_slave_lock);
>  		bond_for_each_slave(bond, slave, iter) {
> -			if ((bond->params.mode == BOND_MODE_ACTIVEBACKUP)
> +			if (USES_PRIMARY(bond->params.mode)
>  				&& (slave != bond->curr_active_slave)) {
>  				bond_set_slave_inactive_flags(slave,
>  							      BOND_SLAVE_NOTIFY_NOW);
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v3] bonding: Inactive slaves should keep inactive flag's value
  2014-04-02  3:01 [PATCH v3] bonding: Inactive slaves should keep inactive flag's value Zheng Li
  2014-04-03  2:16 ` zheng.li
@ 2014-04-04 14:04 ` David Miller
  1 sibling, 0 replies; 3+ messages in thread
From: David Miller @ 2014-04-04 14:04 UTC (permalink / raw)
  To: zheng.x.li
  Cc: netdev, j.vosburgh, fubar, andy, vfalico, linux-kernel, joe.jin

From: Zheng Li <zheng.x.li@oracle.com>
Date: Wed,  2 Apr 2014 11:01:48 +0800

> bond_open is not setting the inactive flag correctly for some modes (alb and
> tlb), resulting in error behavior if the bond has been administratively set
> down and then back up. This effect should not occur when slaves are added while
> the bond is up; it's something that only happens after a down/up bounce of the
> bond.
> 
> For example, in bond tlb or alb mode, domu send some ARP request which go out
> from dom0 bond's active slave, then the ARP broadcast request packets go back to
> inactive slave from switch, because the inactive slave's inactive flag is zero,
> kernel will receive the packets and pass them to bridge that cause dom0's bridge
> map domu's MAC address to port of bond, bridge should map domu's MAC to port of
> vif.
> 
> Signed-off-by: Zheng Li <zheng.x.li@oracle.com>
> Signed-off-by: Jay Vosburgh <j.vosburgh@gmail.com>

Applied.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-04-04 14:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-02  3:01 [PATCH v3] bonding: Inactive slaves should keep inactive flag's value Zheng Li
2014-04-03  2:16 ` zheng.li
2014-04-04 14:04 ` David Miller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).