patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Jianbo Liu <jianbo.liu@linaro.org>
Cc: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	Jan Viktorin <viktorin@rehivetech.com>,
	dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] patch 'eal/ppc: fix file descriptor leak when getting CPU features' has been queued to stable release 16.07.2
Date: Tue, 15 Nov 2016 19:40:22 +0800	[thread overview]
Message-ID: <1479210033-24775-2-git-send-email-yuanhan.liu@linux.intel.com> (raw)
In-Reply-To: <1479210033-24775-1-git-send-email-yuanhan.liu@linux.intel.com>

Hi,

FYI, your patch has been queued to stable release 16.07.2

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable
yet. It will be pushed if I get no objections before 11/19/16.
So please shout if anyone has objections.

Thanks.

	--yliu

---
>From 72db06e6e96e4f62875d5c090cc5e07704192ff0 Mon Sep 17 00:00:00 2001
From: Jianbo Liu <jianbo.liu@linaro.org>
Date: Fri, 4 Nov 2016 15:16:43 +0530
Subject: [PATCH] eal/ppc: fix file descriptor leak when getting CPU features

[ upstream commit 545f16daf6867640261fe7bd263c777a8c61a3c1 ]

Close the file descriptor after finish using it.

Fixes: 9ae15538 ("eal/ppc: cpu flag checks for IBM Power")

Signed-off-by: Jianbo Liu <jianbo.liu@linaro.org>
Acked-by: Jan Viktorin <viktorin@rehivetech.com>
---
 lib/librte_eal/common/arch/ppc_64/rte_cpuflags.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/librte_eal/common/arch/ppc_64/rte_cpuflags.c b/lib/librte_eal/common/arch/ppc_64/rte_cpuflags.c
index a8147c8..fcf96e0 100644
--- a/lib/librte_eal/common/arch/ppc_64/rte_cpuflags.c
+++ b/lib/librte_eal/common/arch/ppc_64/rte_cpuflags.c
@@ -116,6 +116,7 @@ rte_cpu_get_features(hwcap_registers_t out)
 		else if (auxv.a_type == AT_HWCAP2)
 			out[REG_HWCAP2] = auxv.a_un.a_val;
 	}
+	close(auxv_fd);
 }
 
 /*
-- 
1.9.0

  reply	other threads:[~2016-11-15 11:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 11:40 [dpdk-stable] patch 'eal/arm: " Yuanhan Liu
2016-11-15 11:40 ` Yuanhan Liu [this message]
2016-11-15 11:40 ` [dpdk-stable] patch 'lpm: fix freeing memory' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'pci: fix probing error if no driver found' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'net/ixgbe: fix VF registers' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'app/testpmd: fix DCB configuration' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'net/i40e: " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'net/enic: fix max packet length check' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'net/mlx5: fix handling of small mbuf sizes' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'net/mlx5: fix Rx checksum macros' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'net/vmxnet3: fix mbuf release on reset/stop' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'mempool: fix leak if populate fails' " Yuanhan Liu
2016-11-15 11:40 ` [dpdk-stable] patch 'net/virtio: revert fix restart' " Yuanhan Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1479210033-24775-2-git-send-email-yuanhan.liu@linux.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=jianbo.liu@linaro.org \
    --cc=stable@dpdk.org \
    --cc=viktorin@rehivetech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).