From: Thomas Monjalon <thomas@monjalon.net>
To: Radoslaw Biernacki <radoslaw.biernacki@linaro.org>
Cc: stable@dpdk.org, dev@dpdk.org, sergio.gonzalez.monroy@intel.com
Subject: Re: [dpdk-stable] [PATCH] test/memzone: fixing memory leak in memzone autotest
Date: Sat, 11 Nov 2017 12:26:19 +0100 [thread overview]
Message-ID: <2265238.loL1tUXyfP@xps> (raw)
In-Reply-To: <1510144394-31678-1-git-send-email-radoslaw.biernacki@linaro.org>
08/11/2017 13:33, Radoslaw Biernacki:
> This patch fixes the memory leaks in memzone_autotest. Those memory leaks
> lead to failures in tests from the same testing group due to out of memory
> problems. With introduction of rte_memzone_free() it is now possible to
> free the memzone. Fix uses this API call to make a clean after each test
> case.
>
> Fixes: ff909fe21f0a ("mem: introduce memzone freeing")
>
> Signed-off-by: Radoslaw Biernacki <radoslaw.biernacki@linaro.org>
Applied, thanks
prev parent reply other threads:[~2017-11-11 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 12:33 Radoslaw Biernacki
2017-11-11 11:26 ` Thomas Monjalon [this message]
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=2265238.loL1tUXyfP@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=radoslaw.biernacki@linaro.org \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=stable@dpdk.org \
/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).