[dpdk-dev] [PATCH] devargs: do not replace already inserted devargs

Thomas Monjalon thomas at monjalon.net
Mon Nov 12 00:12:32 CET 2018


08/11/2018 18:12, Zhang, Qi Z:
> From: Thomas Monjalon [mailto:thomas at monjalon.net]
> > 08/11/2018 12:25, Stojaczyk, Dariusz:
> > > From: Thomas Monjalon [mailto:thomas at monjalon.net]
> > > >
> > > > The devargs of a device can be replaced by a newly allocated one
> > > > when trying to probe again the same device (multi-process or
> > > > multi-ports scenarios). This is breaking some pointer references.
> > > >
> > > > It can be avoided by copying the new content, freeing the new
> > > > devargs, and returning the already inserted pointer.
> > > >
> > > > Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
> > >
> > > Tested-by: Darek Stojaczyk <dariusz.stojaczyk at intel.com>
> > 
> > Is it fixing any use case?
> 
> Tested-by: Qi Zhang <qi.z.zhang at intel.com>
> 
> The patch also fix below scenario
> 
> attach net_af_packet,iface=enp50s0f0
> attach net_af_packet,iface=enp50s0f0 (failed as expected) 
> detach net_af_packet (failed)

Applied





More information about the dev mailing list