From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] devargs: do not replace already inserted devargs Date: Thu, 08 Nov 2018 13:26:17 +0100 Message-ID: <7262839.kmssWOtaOX@xps> References: <20181107232105.19187-1-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, "gaetan.rivet@6wind.com" , "Zhang, Qi Z" , "Guo, Jia" To: "Stojaczyk, Dariusz" Return-path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 4753649E0 for ; Thu, 8 Nov 2018 13:26:29 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 08/11/2018 12:25, Stojaczyk, Dariusz: > From: Thomas Monjalon [mailto:thomas@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 > > Tested-by: Darek Stojaczyk Is it fixing any use case?