From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] bus/vdev: add warning for duplicated vdev name Date: Wed, 19 Dec 2018 03:26:36 +0100 Message-ID: <1682296.hbgUrQPOuL@xps> References: <20181129071608.20820-1-yahui.cao@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, ferruh.yigit@intel.com To: Yahui Cao Return-path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id ECE291B581 for ; Wed, 19 Dec 2018 03:26:39 +0100 (CET) In-Reply-To: <20181129071608.20820-1-yahui.cao@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 29/11/2018 08:16, Yahui Cao: > If duplicated vdev name is detected, print out a warning message. > > Signed-off-by: Yahui Cao > --- > drivers/bus/vdev/vdev.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/bus/vdev/vdev.c b/drivers/bus/vdev/vdev.c > index 9c66bdc78..ff2db7d3f 100644 > --- a/drivers/bus/vdev/vdev.c > +++ b/drivers/bus/vdev/vdev.c > @@ -462,6 +462,8 @@ vdev_scan(void) > if (find_vdev(devargs->name)) { > rte_spinlock_recursive_unlock(&vdev_device_list_lock); > free(dev); > + VDEV_LOG(WARNING, "duplicated vdev name %s detected!", > + devargs->name); > continue; > } I'm surprised there is nothing to prevent from creating 2 vdevs with the same name. It should be considered as an error and reject the vdev creation.