From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Chas Williams <3chas3@gmail.com>, dev@dpdk.org
Cc: declan.doherty@intel.com, Chas Williams <chas3@att.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 2/2] net/bonding: always update bonding link status
Date: Thu, 14 Jun 2018 18:05:57 +0100 [thread overview]
Message-ID: <e4d28968-b05c-d9cb-1840-b492ae8b86fe@intel.com> (raw)
In-Reply-To: <20180517232252.19908-2-3chas3@gmail.com>
On 5/18/2018 12:22 AM, Chas Williams wrote:
> From: Chas Williams <chas3@att.com>
>
> When the first ETH_LINK_UP slave is added to a bonding device, it is
> immediately activated. If these are polling slaves, there will be a
> later link state event, when last_link_status doesn't match link_status.
> But because this slave is already activated, the bonding device's link
> status isn't updated.
>
> To fix this, we always attempt to update the bonding device's link status
> in the link state change callback.
>
> Fixes: 46fb43683679 ("bond: add mode 4")
> Cc: stable@dpdk.org
>
> Signed-off-by: Chas Williams <chas3@att.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-06-14 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 23:22 [dpdk-stable] [PATCH 1/2] net/bonding: export mode 4 slave info routine Chas Williams
2018-05-17 23:22 ` [dpdk-stable] [PATCH 2/2] net/bonding: always update bonding link status Chas Williams
2018-06-14 17:05 ` Ferruh Yigit [this message]
2018-05-22 10:05 ` [dpdk-stable] [PATCH 1/2] net/bonding: export mode 4 slave info routine Ferruh Yigit
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=e4d28968-b05c-d9cb-1840-b492ae8b86fe@intel.com \
--to=ferruh.yigit@intel.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).