From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id A70949AB7 for ; Tue, 10 May 2016 19:06:42 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP; 10 May 2016 10:06:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,605,1455004800"; d="scan'208";a="803195255" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.87]) ([10.237.220.87]) by orsmga003.jf.intel.com with ESMTP; 10 May 2016 10:06:08 -0700 To: Daniel Mrzyglod , cristian.dumitrescu@intel.com References: <1462875064-119474-1-git-send-email-danielx.t.mrzyglod@intel.com> Cc: dev@dpdk.org From: Ferruh Yigit Message-ID: <57321500.6030906@intel.com> Date: Tue, 10 May 2016 18:06:08 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <1462875064-119474-1-git-send-email-danielx.t.mrzyglod@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH] sched: fix useless call X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 17:06:43 -0000 On 5/10/2016 11:11 AM, Daniel Mrzyglod wrote: > Fix issue reported by Coverity. > Coverity ID 13338 > > A function call that seems to have an intended effect has no actual effect > on the logic of the program. > > In rte_sched_port_free: A function is called that is only useful for its > return value, and this value is ignored. > > Fixes: de3cfa2c9823 ("sched: initial import") > > Signed-off-by: Daniel Mrzyglod > --- > lib/librte_sched/rte_sched.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/lib/librte_sched/rte_sched.c b/lib/librte_sched/rte_sched.c > index 1609ea8..9b962a6 100644 > --- a/lib/librte_sched/rte_sched.c > +++ b/lib/librte_sched/rte_sched.c > @@ -749,7 +749,6 @@ rte_sched_port_free(struct rte_sched_port *port) > rte_pktmbuf_free(mbufs[i]); > } > > - rte_bitmap_free(port->bmp); > rte_free(port); > } > > rte_bitmap_free() just does NULL check on port->bmp. I thought intention can be to free the "bmp", but this isn't the case: port->bmp is actually port->bmp_array, port->bmp_array points somewhere within port->memory, port->memory (zero sized array) allocated and freed with "port" pointer. So for this patch: Acked-by: "Ferruh Yigit " But as follow up: rte_bitmap_free() seems only used here, and it does nothing more than NULL check, with a misleading name, should we remove this function? Regards, ferruh