From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Xueming(steven) Li" <xuemingl@mellanox.com>
Subject: Re: [dpdk-stable] [PATCH] app/testpmd: fix crash when attaching a device
Date: Thu, 14 Jun 2018 16:19:08 +0100 [thread overview]
Message-ID: <0be3cf07-b9ba-e6c0-9d25-bcc8864582cb@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260CB3805@IRSMSX108.ger.corp.intel.com>
On 6/14/2018 3:56 PM, Iremonger, Bernard wrote:
>
>
>> -----Original Message-----
>> From: Adrien Mazarguil [mailto:adrien.mazarguil@6wind.com]
>> Sent: Wednesday, June 13, 2018 5:28 PM
>> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
>> <jingjing.wu@intel.com>; Iremonger, Bernard
>> <bernard.iremonger@intel.com>
>> Cc: dev@dpdk.org; stable@dpdk.org; Singh, Jasvinder
>> <jasvinder.singh@intel.com>; Xueming(steven) Li
>> <xuemingl@mellanox.com>
>> Subject: [PATCH] app/testpmd: fix crash when attaching a device
>>
>> Below commit checks global device information to determine if a port uses
>> the softnic driver once initialized. Problem is that this information is not
>> available at this point when a port is initialized interactively through a "port
>> attach XXX" command, crashing testpmd.
>>
>> This patch systematically initializes global device information to address this
>> issue.
>>
>> Fixes: 5b590fbe09b6 ("app/testpmd: add traffic management forwarding
>> mode")
>> Cc: stable@dpdk.org
>> Cc: Jasvinder Singh <jasvinder.singh@intel.com>
>>
>> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>> ---
>
> Acked-by: Bernard Iremonger <Bernard.iremonger@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-06-14 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 16:27 Adrien Mazarguil
2018-06-14 14:56 ` Iremonger, Bernard
2018-06-14 15:19 ` Ferruh Yigit [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=0be3cf07-b9ba-e6c0-9d25-bcc8864582cb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--cc=xuemingl@mellanox.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).