From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Ajith Adapa <adapa.ajith@gmail.com>,
Jay Vosburgh <jay.vosburgh@canonical.com>,
vfalico@gmail.com, gospo@cumulusnetworks.com,
netdev@vger.kernel.org
Subject: Please backport 63b46242f707849 [was: Issue with LACP mode in linux bonding driver]
Date: Thu, 02 Jul 2015 17:29:38 -0400 [thread overview]
Message-ID: <5595AD42.3040903@cumulusnetworks.com> (raw)
In-Reply-To: <CADAe=++oN6FdmzqrzvXvT+83sS6mjSUDedmWMW6Vgh16M50ATA@mail.gmail.com>
Please back port the following to the LTS trees v3.2, v3.4, v3.10,
v3.12, v3.14, and v3.18
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
Sending this to verify the above patch is being backported to the trees
listed. Have verified this patch does not exist in them currently. The
patch fixes LACP mux machine state changes which if incorrect can cause
a partner switch to send duplicate frames to a Linux host. This patch
has been verified to fix a problem seen on a v3.10 system, and Cumulus
is shipping this patch on kernel versions as old as v3.2.
Thank you,
-Jon
prev parent reply other threads:[~2015-07-02 21:29 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
2015-06-27 2:27 ` Ajith Adapa
2015-07-02 21:29 ` Jonathan Toppins [this message]
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=5595AD42.3040903@cumulusnetworks.com \
--to=jtoppins@cumulusnetworks.com \
--cc=adapa.ajith@gmail.com \
--cc=davem@davemloft.net \
--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).