From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mem: fix static analysis warning Date: Fri, 20 Jul 2018 11:30:00 +0200 Message-ID: <2541590.gd5fToPQqf@xps> References: <8308ba8ca44234ec58b36c422ff3bb85117ecd08.1531841506.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Anatoly Burakov Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id CE3E098 for ; Fri, 20 Jul 2018 11:30:04 +0200 (CEST) In-Reply-To: <8308ba8ca44234ec58b36c422ff3bb85117ecd08.1531841506.git.anatoly.burakov@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" 17/07/2018 17:41, Anatoly Burakov: > Technically, single file segments codepath will never get > triggered when using in-memory mode, because EAL prohibits > mixing these two options at initialization time. However, > code analyzers do not know that, and some will complain > about either using uninitialized variables, or trying to > do operations on an already closed descriptor. > > Fix this by assuring the compiler or code analyzer that > in-memory mode code never gets triggered when using > single-file segments mode. > > Coverity ID: 302847 > Fixes: 72b49ff623c4 ("mem: support --in-memory mode") > > Signed-off-by: Anatoly Burakov Applied, thanks