From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Burakov, Anatoly" Subject: Re: [PATCH 00/10] Coverity fixes for EAL memory Date: Tue, 17 Apr 2018 17:09:37 +0100 Message-ID: <1f840947-c8ab-3fe1-4b00-3fd4a14e135b@intel.com> References: <2822934.JnSj6TxSKo@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 28FF6D592 for ; Tue, 17 Apr 2018 18:09:40 +0200 (CEST) In-Reply-To: <2822934.JnSj6TxSKo@xps> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 17-Apr-18 4:56 PM, Thomas Monjalon wrote: > 17/04/2018 17:50, Anatoly Burakov: >> This patchset fixes a host of coverity issues in memory subsystem >> introduced with recent DPDK memory hotplug patchset. >> >> Coverity issues fixed: >> - 272601 - leaking fd >> - 272560 - double close fd >> - 272568 - leaking fd >> - 272570 - leaking fd >> - 272589 - dereference before null check >> - 272602 - freeing wrong pointer >> - 272608 - expression does nothing >> - 272577 - negative return not handled >> - 272578 - negative return not handled >> - 272584 - use after free > > Looks like you should buy a Coverity license > to run it locally before submitting ;) > Well, in fairness, most of these issues (and similar issues submitted in another patchset) will not ever manifest themselves under normal circumstances, so it's not as bad as it perhaps might present itself. -- Thanks, Anatoly