netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Jonathan Toppins <jtoppins@cumulusnetworks.com>
Cc: Veaceslav Falico <vfalico@gmail.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	netdev@vger.kernel.org, Wilson Kok <wkok@cumulusnetworks.com>,
	Andy Gospodarek <gospo@cumulusnetworks.com>
Subject: Re: [PATCH net-next v2 2/5] bonding: fix bond_open() don't always set slave active flag
Date: Mon, 26 Jan 2015 16:33:24 -0800	[thread overview]
Message-ID: <21599.1422318804@famine> (raw)
In-Reply-To: <1422253021-3798-3-git-send-email-jtoppins@cumulusnetworks.com>

Jonathan Toppins <jtoppins@cumulusnetworks.com> wrote:

>From: Wilson Kok <wkok@cumulusnetworks.com>
>
>Mode 802.3ad, fix incorrect bond slave active state when slave is not in
>active aggregator. During bond_open(), the bonding driver always sets
>the slave active flag to true if the bond is not in active-backup, alb,
>or tlb modes. Bonding should let the aggregator selection logic set the
>active flag when in 802.3ad mode.
>
>Cc: Andy Gospodarek <gospo@cumulusnetworks.com>
>Reviewed-by: Nikolay Aleksandrov <nikolay@redhat.com>
>Signed-off-by: Wilson Kok <wkok@cumulusnetworks.com>
>Signed-off-by: Jonathan Toppins <jtoppins@cumulusnetworks.com>

Signed-off-by: Jay Vosburgh <jay.vosburgh@canonical.com>

>---
> drivers/net/bonding/bond_main.c |    2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
>index 02ffedb..c475d90 100644
>--- a/drivers/net/bonding/bond_main.c
>+++ b/drivers/net/bonding/bond_main.c
>@@ -3066,7 +3066,7 @@ static int bond_open(struct net_device *bond_dev)
> 			    slave != rcu_access_pointer(bond->curr_active_slave)) {
> 				bond_set_slave_inactive_flags(slave,
> 							      BOND_SLAVE_NOTIFY_NOW);
>-			} else {
>+			} else if (BOND_MODE(bond) != BOND_MODE_8023AD) {
> 				bond_set_slave_active_flags(slave,
> 							    BOND_SLAVE_NOTIFY_NOW);
> 			}
>-- 
>1.7.10.4
>

  reply	other threads:[~2015-01-27  0:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26  6:16 [PATCH net-next v2 0/5] bonding: various 802.3ad fixes Jonathan Toppins
2015-01-26  6:16 ` [PATCH net-next v2 1/5] bonding: update bond carrier state when min_links option changes Jonathan Toppins
2015-01-27  0:29   ` Jay Vosburgh
2015-01-26  6:16 ` [PATCH net-next v2 2/5] bonding: fix bond_open() don't always set slave active flag Jonathan Toppins
2015-01-27  0:33   ` Jay Vosburgh [this message]
2015-01-26  6:16 ` [PATCH net-next v2 3/5] bonding: fix incorrect lacp mux state when agg not active Jonathan Toppins
2015-01-27  2:42   ` Jay Vosburgh
2015-01-26  6:17 ` [PATCH net-next v2 4/5] bonding: fix LACP PDU not sent on slave port sometimes Jonathan Toppins
2015-01-26 12:04   ` Sergei Shtylyov
2015-01-27  0:45     ` Jay Vosburgh
2015-01-26  6:17 ` [PATCH net-next v2 5/5] bonding: cleanup and remove dead code Jonathan Toppins
2015-01-27  0:46   ` Jay Vosburgh
2015-01-27  0:49 ` [PATCH net-next v2 0/5] bonding: various 802.3ad fixes Andy Gospodarek
2015-01-28  1:09 ` David Miller

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=21599.1422318804@famine \
    --to=jay.vosburgh@canonical.com \
    --cc=andy@greyhouse.net \
    --cc=gospo@cumulusnetworks.com \
    --cc=jtoppins@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=vfalico@gmail.com \
    --cc=wkok@cumulusnetworks.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).