From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 1/2] net/i40e: fix segmentation fault in close
Date: Fri, 20 Jan 2017 13:15:24 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810CCE631@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1484671162-18493-2-git-send-email-bernard.iremonger@intel.com>
> -----Original Message-----
> From: Iremonger, Bernard
> Sent: Wednesday, January 18, 2017 12:39 AM
> To: dev@dpdk.org; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Zhang, Helin <helin.zhang@intel.com>
> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>; stable@dpdk.org
> Subject: [PATCH v4 1/2] net/i40e: fix segmentation fault in close
>
> Change the order of releasing the vsi's.
> Release the vmdq vsi's first, then release the main vsi.
>
> Fixes: 4861cde46116 ("i40e: new poll mode driver")
>
> CC: stable@dpdk.org
>
> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
next prev parent reply other threads:[~2017-01-20 13:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 16:29 [dpdk-dev] [PATCH v2 0/2] net/i40e: fix segmentation fault Bernard Iremonger
2017-01-09 16:29 ` [dpdk-dev] [PATCH v2 1/2] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-09 16:29 ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-12 13:58 ` [dpdk-dev] [PATCH v3 0/2] net/i40e: fix segmentation fault Bernard Iremonger
2017-01-17 16:39 ` [dpdk-dev] [PATCH v4 " Bernard Iremonger
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 0/3] " Bernard Iremonger
2017-01-27 10:49 ` [dpdk-dev] [PATCH v6 0/2] app/testpmd: enable VMDq in testpmd Bernard Iremonger
2017-01-27 10:49 ` [dpdk-dev] [PATCH v6 1/2] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-27 10:50 ` [dpdk-dev] [PATCH v6 2/2] app/testpmd: fix port stop Bernard Iremonger
2017-02-03 8:21 ` Wu, Jingjing
2017-02-03 10:37 ` Iremonger, Bernard
2017-02-12 4:34 ` Wu, Jingjing
2017-03-10 13:17 ` Thomas Monjalon
2017-03-10 16:56 ` Wu, Jingjing
2017-03-10 16:59 ` Iremonger, Bernard
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 1/3] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 2/3] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 3/3] app/testpmd: fix port stop Bernard Iremonger
2017-01-17 16:39 ` [dpdk-dev] [PATCH v4 1/2] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-20 13:15 ` Wu, Jingjing [this message]
2017-01-17 16:39 ` [dpdk-dev] [PATCH v4 2/2] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-20 13:33 ` Wu, Jingjing
2017-01-20 15:22 ` Iremonger, Bernard
2017-01-12 13:58 ` [dpdk-dev] [PATCH v3 1/2] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-17 14:34 ` Wu, Jingjing
2017-01-17 16:30 ` Iremonger, Bernard
2017-01-12 13:58 ` [dpdk-dev] [PATCH v3 2/2] app/testpmd: add command to configure VMDq Bernard Iremonger
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=9BB6961774997848B5B42BEC655768F810CCE631@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.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).