From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] vhost: fix false-positive warning from clang 5 Date: Wed, 11 Oct 2017 14:49:23 +0200 Message-ID: <188478579.ZJIaHkYeo6@xps> References: <20171011095907.229893-1-bruce.richardson@intel.com> <20171011112817.3357-1-bruce.richardson@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, yliu@fridaylinux.org, Maxime Coquelin To: Bruce Richardson Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id E252D2C37 for ; Wed, 11 Oct 2017 14:49:24 +0200 (CEST) In-Reply-To: <20171011112817.3357-1-bruce.richardson@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" 11/10/2017 13:28, Bruce Richardson: > When compiling with clang extra warning flags, such as used by default with > meson, a warning is given in iotlb.c: > > ../lib/librte_vhost/iotlb.c:318:6: warning: variable 'socket' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized] > > This is a false positive, as the socket value will be initialized by the > call to get_mempolicy in the case where the NUMA build-time flag is set, > and in cases where it is not set, "if (ret)" will always be true as ret is > initialized to -1 and never changed. > > However, this is not immediately obvious, and is perhaps a little fragile, > as it will break if other code using ret is subsequently added above the > call to get_mempolicy by someone unaware of this subtle dependency. > Therefore, we can fix the warning and making the code more robust by > explicitly initializing socket to zero, and moving the extra condition > check on the return from get_mempolicy() into the #ifdef > > Fixes: d012d1f293f4 ("vhost: add IOTLB helper functions") > > CC: Maxime Coquelin > Signed-off-by: Bruce Richardson Applied, thanks