Re: [dpdk-dev] [PATCH v3] dev: don't remove devargs that are still referenced

23/11/2018 18:04, Maxime Coquelin: > Hi, > > On 11/23/18 4:43 PM, Darek Stojaczyk wrote: > > Even if a device failed to plug, it's still a device > > object that references the devargs. Those devargs will > > be freed automatically together with the device, but > > freeing them any earlier - like

Re: [dpdk-dev] [PATCH v3] dev: don't remove devargs that are still referenced

> -Original Message- > From: Maxime Coquelin [mailto:maxime.coque...@redhat.com] > Sent: Friday, November 23, 2018 6:05 PM > To: Stojaczyk, Dariusz ; dev@dpdk.org > Cc: gaetan.ri...@6wind.com; tho...@monjalon.net > Subject: Re: [dpdk-dev] [PATCH v3] dev: don't

Re: [dpdk-dev] [PATCH v3] dev: don't remove devargs that are still referenced

Hi, On 11/23/18 4:43 PM, Darek Stojaczyk wrote: Even if a device failed to plug, it's still a device object that references the devargs. Those devargs will be freed automatically together with the device, but freeing them any earlier - like it's done in the hotplug error handling path right now

[dpdk-dev] [PATCH v3] dev: don't remove devargs that are still referenced

Even if a device failed to plug, it's still a device object that references the devargs. Those devargs will be freed automatically together with the device, but freeing them any earlier - like it's done in the hotplug error handling path right now - will give us a dangling pointer and a segfault sc