[dpdk-dev] [PATCH] drivers/net: fix segfault in secondary process

Zhang, Qi Z qi.z.zhang at intel.com
Fri Jul 20 00:19:15 CEST 2018



> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Friday, July 20, 2018 12:46 AM
> To: John W. Linville <linville at tuxdriver.com>; Doherty, Declan
> <declan.doherty at intel.com>; Chas Williams <chas3 at att.com>; Gaetan Rivet
> <gaetan.rivet at 6wind.com>; Tetsuya Mukawa <mtetsuyah at gmail.com>;
> Santosh Shukla <santosh.shukla at caviumnetworks.com>; Jerin Jacob
> <jerin.jacob at caviumnetworks.com>; Wiles, Keith <keith.wiles at intel.com>;
> Maxime Coquelin <maxime.coquelin at redhat.com>; Bie, Tiwei
> <tiwei.bie at intel.com>; Wang, Zhihong <zhihong.wang at intel.com>
> Cc: dev at dpdk.org; Yigit, Ferruh <ferruh.yigit at intel.com>; stable at dpdk.org;
> Varghese, Vipin <vipin.varghese at 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 at dpdk.org
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit at 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 at intel.com>


More information about the dev mailing list