From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mempool: fix local cache initialization
Date: Thu, 9 Jun 2016 08:57:02 +0100 [thread overview]
Message-ID: <1cafd17e-ffe1-83cc-e745-d3dedc5d44cf@intel.com> (raw)
In-Reply-To: <57586EAC.7090304@6wind.com>
Hi Olivier,
On 08/06/2016 20:14, Olivier Matz wrote:
> Hi Sergio,
>
> Good catch, thanks. The patch looks ok, just few comments
> on the commit log:
>
> On 06/08/2016 05:10 PM, Sergio Gonzalez Monroy wrote:
>> The mempool local cache is not being initialize properly leading to
> 'initialize' -> 'initialized' ?
> and maybe 'is not being' -> 'was not' ?
>
>> undefined behavior in cases where the allocated memory was used and left
>> with data.
>>
>> Fixes: af75078fece3 ("first public release")
> I think it fixes this one instead:
>
> 213af31e0960 ("mempool: reduce structure size if no cache needed")
Fair enough, I thought the issue was there as we never
initialized/zeroed the local cache
on mempool creation. Usually we would have allocated all mempools on
init (or close)
and that would be it (initially all memory would be zeroed), but I think
you could still
manage to reproduce the problem if somehow you where to do something like:
rte_malloc(), rte_free(), rte_mempool_create() and the memory was the
one we got
with malloc and never gets zeroed again.
Sergio
next prev parent reply other threads:[~2016-06-09 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 15:10 Sergio Gonzalez Monroy
2016-06-08 19:14 ` Olivier Matz
2016-06-09 7:57 ` Sergio Gonzalez Monroy [this message]
2016-06-09 8:03 ` Olivier Matz
2016-06-09 8:14 ` Sergio Gonzalez Monroy
2016-06-09 8:19 ` [dpdk-dev] [PATCH v2] " Sergio Gonzalez Monroy
2016-06-09 8:26 ` Olivier Matz
2016-06-15 13:59 ` 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=1cafd17e-ffe1-83cc-e745-d3dedc5d44cf@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).