netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ding Tianhong <dingtianhong@huawei.com>
To: "zheng.li" <zheng.x.li@oracle.com>
Cc: <netdev@vger.kernel.org>, <fubar@us.ibm.com>,
	<andy@greyhouse.net>, <linux-kernel@vger.kernel.org>,
	<davem@davemloft.net>, <joe.jin@oracle.com>
Subject: Re: [PATCH] bonding: Inactive slaves should keep inactive flag's value to 1 in tlb and alb mode.
Date: Wed, 26 Mar 2014 08:53:14 +0800	[thread overview]
Message-ID: <533224FA.6040307@huawei.com> (raw)
In-Reply-To: <53314017.8040104@oracle.com>

On 2014/3/25 16:36, zheng.li wrote:
> 于 2014年03月25日 11:42, Ding Tianhong 写道:
>> On 2014/3/25 11:00, Zheng Li wrote:
>>> In bond mode tlb and alb, inactive slaves should keep inactive flag to
>>> 1 to refuse to receive broadcast packets. Now, active slave send broadcast packets
>>> (for example ARP requests) which will arrive inactive slaves on same host from switch,
>>> but inactive slave's inactive flag is zero that cause bridge receive the broadcast
>>> packets to produce a wrong entry in forward table. Typical situation is 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>
>>> ---
>>>  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..8761df6 100644
>>> --- a/drivers/net/bonding/bond_main.c
>>> +++ b/drivers/net/bonding/bond_main.c
>>> @@ -3062,7 +3062,7 @@ static int bond_open(struct net_device *bond_dev)
>>>  				&& (slave != bond->curr_active_slave)) {
>>>  				bond_set_slave_inactive_flags(slave,
>>>  							      BOND_SLAVE_NOTIFY_NOW);
>>> -			} else {
>>> +			} else if (!bond_is_lb(bond)) {
>>>  				bond_set_slave_active_flags(slave,
>>>  							    BOND_SLAVE_NOTIFY_NOW);
>>>  			}
>>>
>> I think you did not fix the problem completely, the state monitor will change the status for the slaves
>> and the inactive slave still could receive the broadcast.
> 
> Had tested, it can fix the issue, verified by our QA.
> Default set slave of bond as inactive when add a slave to bond, when
> link UP, just set one slave as current active slave and clear its
> inactive flag, the inactive slave's inactive flag will keep the value of 1.
> 
> 
Ok, I found that in the mii monitor, it will only change the backup state, no problem,
it looks good to me.

Ding

>>
>> Regards
>> Ding
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 
> 
> .
> 

  reply	other threads:[~2014-03-26  0:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  3:00 [PATCH] bonding: Inactive slaves should keep inactive flag's value to 1 in tlb and alb mode Zheng Li
2014-03-25  3:42 ` Ding Tianhong
2014-03-25  8:36   ` zheng.li
2014-03-26  0:53     ` Ding Tianhong [this message]
2014-03-27  2:26       ` zheng.li
2014-03-27 17:23 ` Jay Vosburgh
2014-03-28  8:39   ` zheng.li
2014-04-02  7:35 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533224FA.6040307@huawei.com \
    --to=dingtianhong@huawei.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=joe.jin@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=zheng.x.li@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).