From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Marcin Kerlin <marcinx.kerlin@intel.com>, david.marchand@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/1] eal: fix resource leak of mapped memory
Date: Wed, 15 Jun 2016 09:49:04 +0100 [thread overview]
Message-ID: <a28ccd24-eb9c-f711-517e-b486c0786930@intel.com> (raw)
In-Reply-To: <1465918435-30973-1-git-send-email-marcinx.kerlin@intel.com>
Hi Marcin,
On 14/06/2016 16:33, Marcin Kerlin wrote:
> Patch fixes resource leak in rte_eal_hugepage_attach() where mapped files
> were not freed back to the OS in case of failure. Patch uses the behavior
> of Linux munmap: "It is not an error if the indicated range does not
> contain any mapped pages".
>
> Coverity issue: 13295, 13296, 13303
> Fixes: af75078fece3 ("first public release")
>
> Signed-off-by: Marcin Kerlin <marcinx.kerlin@intel.com>
> ---
> lib/librte_eal/linuxapp/eal/eal_memory.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_memory.c b/lib/librte_eal/linuxapp/eal/eal_memory.c
> index 79d1d2d..1834fa0 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_memory.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_memory.c
> @@ -1417,7 +1417,7 @@ rte_eal_hugepage_attach(void)
> if (internal_config.xen_dom0_support) {
> #ifdef RTE_LIBRTE_XEN_DOM0
> if (rte_xen_dom0_memory_attach() < 0) {
> - RTE_LOG(ERR, EAL,"Failed to attach memory setments of primay "
> + RTE_LOG(ERR, EAL, "Failed to attach memory segments of primary "
> "process\n");
If you want to fix spelling of error message it probably should go in a
different patch.
> return -1;
> }
> @@ -1481,7 +1481,7 @@ rte_eal_hugepage_attach(void)
>
> size = getFileSize(fd_hugepage);
> hp = mmap(NULL, size, PROT_READ, MAP_PRIVATE, fd_hugepage, 0);
> - if (hp == NULL) {
> + if (hp == MAP_FAILED) {
> RTE_LOG(ERR, EAL, "Could not mmap %s\n", eal_hugepage_info_path());
> goto error;
> }
> @@ -1551,6 +1551,13 @@ rte_eal_hugepage_attach(void)
> return 0;
>
> error:
> + s = 0;
> + while (s < RTE_MAX_MEMSEG && mcfg->memseg[s].len > 0) {
> + munmap(mcfg->memseg[s].addr, mcfg->memseg[s].len);
> + s++;
> + }
> + if (hp != NULL && hp != MAP_FAILED)
> + munmap((void *)(uintptr_t)hp, size);
No need for double casting, nor to cast to (void *).
Sergio
> if (fd_zero >= 0)
> close(fd_zero);
> if (fd_hugepage >= 0)
next prev parent reply other threads:[~2016-06-15 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 16:27 [dpdk-dev] [PATCH 1/1] lib/librte_eal: fix resource leak Marcin Kerlin
2016-04-20 9:15 ` David Marchand
2016-04-21 11:19 ` Sergio Gonzalez Monroy
2016-04-21 11:49 ` Kerlin, MarcinX
2016-04-22 10:42 ` Panu Matilainen
2016-06-14 15:33 ` [dpdk-dev] [PATCH v2 1/1] eal: fix resource leak of mapped memory Marcin Kerlin
2016-06-15 8:49 ` Sergio Gonzalez Monroy [this message]
2016-06-15 9:35 ` Kerlin, MarcinX
2016-06-15 10:05 ` Panu Matilainen
2016-06-15 11:13 ` Kerlin, MarcinX
2016-06-15 10:45 ` [dpdk-dev] [PATCH v3 " Marcin Kerlin
2016-06-15 12:25 ` [dpdk-dev] [PATCH v4 " Marcin Kerlin
2016-06-16 12:57 ` Sergio Gonzalez Monroy
2016-06-16 15:14 ` [dpdk-dev] [PATCH v5 " Marcin Kerlin
2016-06-20 9:30 ` Thomas Monjalon
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=a28ccd24-eb9c-f711-517e-b486c0786930@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=marcinx.kerlin@intel.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).