> -----Original Message----- > From: Thomas Monjalon [mailto:[email protected]] > Sent: Thursday, November 8, 2018 12:21 AM > To: [email protected] > Cc: [email protected]; Zhang, Qi Z <[email protected]>; Guo, Jia > <[email protected]>; Stojaczyk, Dariusz <[email protected]> > Subject: [PATCH] devargs: do not replace already inserted devargs > > 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]>
