netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
To: Jay Vosburgh <jay.vosburgh@canonical.com>,
	Ajith Adapa <adapa.ajith@gmail.com>
Cc: vfalico@gmail.com, gospo@cumulusnetworks.com, netdev@vger.kernel.org
Subject: Re: Issue with LACP mode in linux bonding driver
Date: Fri, 26 Jun 2015 19:57:22 -0400	[thread overview]
Message-ID: <558DE6E2.5080207@cumulusnetworks.com> (raw)
In-Reply-To: <13466.1435353566@famine>

On 6/26/15 5:19 PM, Jay Vosburgh wrote:
> Ajith Adapa <adapa.ajith@gmail.com> wrote:
>
>> On 26 June 2015 at 07:45, Jay Vosburgh <jay.vosburgh@canonical.com> wrote:
>>> echo 'module bonding =p' > /sys/kernel/debug/dynamic_debug/control
>> Hi,
>>
>> thanks for the reply.
>
> 	I tried this out a bit here, and could reproduce the problem on
> 3.13, but not on 4.0.0.  A bit of checking suggests that this problem is
> fixed by the following commit:
>
> commit 63b46242f707849a1df10b70e026281bfa40e849
> Author: Wilson Kok <wkok@cumulusnetworks.com>
> Date:   Mon Jan 26 01:16:59 2015 -0500
>
>      bonding: fix incorrect lacp mux state when agg not active
>

Yes this should be picked up by the stable trees, apologies if I dropped 
the ball on cc'ing stable@. We (cumulus) are running a version of this 
patch in 3.2 code, so all stable trees should receive it.

-Jon

  reply	other threads:[~2015-06-26 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADAe=+LvNgHV+crN_+E4xB+Pcz=KSvZpK5ADKzYFjHL2gGJq2Q@mail.gmail.com>
2015-06-26  2:15 ` Issue with LACP mode in linux bonding driver Jay Vosburgh
2015-06-26 13:57   ` Ajith Adapa
2015-06-26 21:19     ` Jay Vosburgh
2015-06-26 23:57       ` Jonathan Toppins [this message]
2015-06-27  2:27         ` Ajith Adapa
2015-07-02 21:29           ` Please backport 63b46242f707849 [was: Issue with LACP mode in linux bonding driver] Jonathan Toppins

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=558DE6E2.5080207@cumulusnetworks.com \
    --to=jtoppins@cumulusnetworks.com \
    --cc=adapa.ajith@gmail.com \
    --cc=gospo@cumulusnetworks.com \
    --cc=jay.vosburgh@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=vfalico@gmail.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).