From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Chas Williams" <chas3@att.com>,
Gaetan Rivet <gaetan.rivet@6wind.com>,
"Tetsuya Mukawa" <mtetsuyah@gmail.com>,
Santosh Shukla <santosh.shukla@caviumnetworks.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Wiles, Keith" <keith.wiles@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Bie, Tiwei" <tiwei.bie@intel.com>,
"Wang, Zhihong" <zhihong.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Varghese, Vipin" <vipin.varghese@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] drivers/net: fix segfault in secondary process
Date: Thu, 19 Jul 2018 22:19:15 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115325C8FB@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180719164556.93162-1-ferruh.yigit@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Friday, July 20, 2018 12:46 AM
> To: John W. Linville <linville@tuxdriver.com>; Doherty, Declan
> <declan.doherty@intel.com>; Chas Williams <chas3@att.com>; Gaetan Rivet
> <gaetan.rivet@6wind.com>; Tetsuya Mukawa <mtetsuyah@gmail.com>;
> Santosh Shukla <santosh.shukla@caviumnetworks.com>; Jerin Jacob
> <jerin.jacob@caviumnetworks.com>; Wiles, Keith <keith.wiles@intel.com>;
> Maxime Coquelin <maxime.coquelin@redhat.com>; Bie, Tiwei
> <tiwei.bie@intel.com>; Wang, Zhihong <zhihong.wang@intel.com>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; stable@dpdk.org;
> Varghese, Vipin <vipin.varghese@intel.com>
> Subject: [dpdk-dev] [PATCH] drivers/net: fix segfault in secondary process
>
> Calling rte_eth_dev_info_get() on secondary process cause a crash because
> eth_dev->device is not set properly.
>
> Fixes: ee27edbe0c10 ("drivers/net: share vdev data to secondary process")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Yes, this is the same issue I met when detaching the device from a secondary process.
The backend device should be assigned on secondary.
Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
next prev parent reply other threads:[~2018-07-19 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 16:45 [dpdk-stable] " Ferruh Yigit
2018-07-19 16:32 ` [dpdk-stable] [dpdk-dev] " Stephen Hemminger
2018-07-20 10:13 ` Ferruh Yigit
2018-07-19 22:19 ` Zhang, Qi Z [this message]
2018-07-20 12:44 ` [dpdk-stable] [PATCH v2] " Ferruh Yigit
2018-07-20 12:23 ` Thomas Monjalon
2018-07-20 13:36 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2018-07-20 14:54 ` [dpdk-stable] [PATCH v3] " Ferruh Yigit
2018-07-26 12:58 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=039ED4275CED7440929022BC67E706115325C8FB@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=chas3@att.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=keith.wiles@intel.com \
--cc=linville@tuxdriver.com \
--cc=maxime.coquelin@redhat.com \
--cc=mtetsuyah@gmail.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=vipin.varghese@intel.com \
--cc=zhihong.wang@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).