From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] eal: Fix resource leak while secondary process maps pci devices Date: Mon, 20 Jun 2016 10:50:33 +0200 Message-ID: <2683003.3TnX10CuWW@xps13> References: <1465961172-28253-1-git-send-email-mukawa@igel.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: David Marchand , dev@dpdk.org, "Mcnamara, John" , michalx.k.jastrzebski@intel.com To: Tetsuya Mukawa Return-path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id C6D7E91BF for ; Mon, 20 Jun 2016 10:50:39 +0200 (CEST) Received: by mail-wm0-f41.google.com with SMTP id v199so59546441wmv.0 for ; Mon, 20 Jun 2016 01:50:39 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-06-20 11:19, Tetsuya Mukawa: > On 2016/06/17 21:28, David Marchand wrote: > > On Thu, Jun 16, 2016 at 4:33 AM, Tetsuya Mukawa wrote: > >> This patch fixes resource leak of pci_uio_map_secondary(). > >> If pci_map_resource() succeeds but mapped address is different from an > >> address primary process mapped, this should be error. > >> Then the addresses secondary process mapped should be freed. > >> > >> Signed-off-by: Tetsuya Mukawa > > > > scripts/check-git-log.sh is not happy : > > > > Wrong headline uppercase: > > eal: Fix resource leak while secondary process maps pci devices > > Wrong headline lowercase: > > eal: Fix resource leak while secondary process maps pci devices > > Headline too long: > > eal: Fix resource leak while secondary process maps pci devices > > Missing 'Fixes' tag: > > eal: Fix resource leak while secondary process maps pci devices > > > > > > checkpatch is not happy, but I think we can ignore it. > > > > WARNING:LONG_LINE: line over 80 characters > > #48: FILE: lib/librte_eal/common/eal_common_pci_uio.c:93: > > + (size_t)uio_res->maps[j].size); > > > > > > Anyways, looks good to me, Thomas, can you fix the commit logs of > > those last 3 patches on eal ? > > Thanks. > > > > Hi David, > > I appreciate your checking. > Next time I will check check-git-log.sh before submitting. > > > Hi Thomas, > > Could you please let me know if you need the fixed patches. Applied, thanks