From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Phil Yang <phil.yang@arm.com>, dev@dpdk.org
Cc: jianbo.liu@arm.com, herbert.guan@arm.com
Subject: Re: [dpdk-dev] [PATCH v2 2/2] test/memzone: Fix test_memzone_free issue
Date: Mon, 15 Jan 2018 09:49:02 +0000 [thread overview]
Message-ID: <85695ff5-75f0-d75a-45a5-ef59f3bd5ec4@intel.com> (raw)
In-Reply-To: <1515995546-5981-3-git-send-email-phil.yang@arm.com>
On 15-Jan-18 5:52 AM, Phil Yang wrote:
> When reserving memzone for mz[], it will out of mz[RTE_MAX_MEMZONE] memory
> bound after the counter reached to RTE_MAX_MEMZONE. It will flush the
> counter's memory and lead to mz[] memory cannot be freed.
>
> Fixd by extend to mz[RTE_MAX_MEMZONE + 1].
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
prev parent reply other threads:[~2018-01-15 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 9:41 [dpdk-dev] [PATCH] test/memzone: Fix test_memzone_basic & test_memzone_free issues Phil Yang
2018-01-12 5:46 ` Jianbo Liu
2018-01-12 17:43 ` Burakov, Anatoly
2018-01-15 5:57 ` Phil Yang
2018-01-15 5:43 ` [dpdk-dev] [PATCH 0/2] Fix memzone autotest issues Phil Yang
2018-01-15 5:43 ` [dpdk-dev] [PATCH 1/2] test/memzone: Fix test_memzone_basic issue Phil Yang
2018-01-15 5:43 ` [dpdk-dev] [PATCH 2/2] test/memzone: Fix test_memzone_free issue Phil Yang
2018-01-17 23:41 ` [dpdk-dev] [PATCH 0/2] Fix memzone autotest issues Thomas Monjalon
2018-01-15 5:52 ` [dpdk-dev] [PATCH v2 " Phil Yang
2018-01-15 5:52 ` [dpdk-dev] [PATCH v2 1/2] test/memzone: Fix test_memzone_basic issue Phil Yang
2018-01-15 9:48 ` Burakov, Anatoly
2018-01-15 5:52 ` [dpdk-dev] [PATCH v2 2/2] test/memzone: Fix test_memzone_free issue Phil Yang
2018-01-15 9:49 ` Burakov, Anatoly [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=85695ff5-75f0-d75a-45a5-ef59f3bd5ec4@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=herbert.guan@arm.com \
--cc=jianbo.liu@arm.com \
--cc=phil.yang@arm.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).