From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] eal: remove call to unlock Date: Wed, 25 Apr 2018 12:32:37 +0200 Message-ID: <1703557.Am3HRJYA0H@xps> References: <9061a11d7dbba7452207c0943b05796f15a0af1d.1524650784.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 out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 156B658FE for ; Wed, 25 Apr 2018 12:32:40 +0200 (CEST) In-Reply-To: <9061a11d7dbba7452207c0943b05796f15a0af1d.1524650784.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" 25/04/2018 12:08, Anatoly Burakov: > Coverity was complaining about not checking result of call to > fcntl() for unlocking the file. Disregarding the fact that error > value returned from fcntl() unlock call is highly unlikely in the > first place, we are subsequently calling close() on that same fd, > which will drop the lock, which makes call to fcntl() unnecessary. > > Fix this by removing a call to fcntl() altogether. > > Coverity issue: 272607 > > Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists") > Cc: anatoly.burakov@intel.com > > Signed-off-by: Anatoly Burakov Applied, thanks