> -----Original Message-----
> From: Thomas Monjalon [mailto:[email protected]]
> Sent: Thursday, November 8, 2018 5:26 AM
> To: Stojaczyk, Dariusz <[email protected]>
> Cc: [email protected]; [email protected]; Zhang, Qi Z
> <[email protected]>; Guo, Jia <[email protected]>
> Subject: Re: [PATCH] devargs: do not replace already inserted devargs
>
> 08/11/2018 12:25, Stojaczyk, Dariusz:
> > From: Thomas Monjalon [mailto:[email protected]]
> > >
> > > 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 <[email protected]>
> >
> > Tested-by: Darek Stojaczyk <[email protected]>
>
> Is it fixing any use case?
Tested-by: Qi Zhang <[email protected]>
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)
Thanks!
Qi
>
