From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Chas Williams <3chas3@gmail.com>,
Jiang JunyuX <junyux.jiang@intel.com>,
dev@dpdk.org
Cc: Chas Williams <chas3@att.com>,
Yang Qiming <qiming.yang@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4] net/bonding: fix invalid port using
Date: Wed, 30 Oct 2019 08:48:10 +0000 [thread overview]
Message-ID: <e5cae81e-efa9-8b5e-037f-826760928d2a@intel.com> (raw)
In-Reply-To: <1f52050c-b5d4-f4b1-c24e-36cef00c2d89@gmail.com>
On 10/29/2019 3:59 PM, Chas Williams wrote:
> On 10/28/19 10:23 PM, Jiang JunyuX wrote:
>> Port validation should be prior to getting device data
>> to avoid segment fault. This patch fixed the segment fault
>> caused by invalid port using.
>>
>> Fixes: 6d72657ce379 ("net/bonding: add other aggregator modes")
>> Fixes: 112891cd27e5 ("net/bonding: add dedicated HW queues for LACP control")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Jiang JunyuX <junyux.jiang@intel.com>
>
> Acked-by: Chas Williams <chas3@att.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-10-30 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 20:55 [dpdk-stable] [PATCH] net/bonding: fix segfault using invalid port Jiang JunyuX
2019-10-28 5:42 ` Yang, Qiming
2019-10-29 3:04 ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
2019-10-29 6:15 ` Yang, Qiming
2019-10-29 6:25 ` Ye Xiaolong
2019-10-29 8:32 ` Yang, Qiming
2019-10-28 20:19 ` [dpdk-stable] [PATCH v2] " Jiang JunyuX
2019-10-28 20:48 ` [dpdk-stable] [PATCH v3] net/bonding: fix invalid port using Jiang JunyuX
2019-10-29 2:23 ` [dpdk-stable] [PATCH v4] " Jiang JunyuX
2019-10-29 15:59 ` [dpdk-stable] [dpdk-dev] " Chas Williams
2019-10-30 8:48 ` Ferruh Yigit [this message]
2019-10-30 2:24 ` [dpdk-stable] " Yang, Qiming
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=e5cae81e-efa9-8b5e-037f-826760928d2a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=junyux.jiang@intel.com \
--cc=qiming.yang@intel.com \
--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).