From: David Marchand <david.marchand@redhat.com>
To: Xueming Li <xuemingl@mellanox.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Cc: Asaf Penso <asafp@mellanox.com>, dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 2/2] malloc: fix realloc padded element size
Date: Tue, 19 Nov 2019 21:47:15 +0100 [thread overview]
Message-ID: <CAJFAV8xieOuFRQpBQhOERUqS7372774H=qk9eO4iy86ku79fpQ@mail.gmail.com> (raw)
In-Reply-To: <1573570228-15676-2-git-send-email-xuemingl@mellanox.com>
On Tue, Nov 12, 2019 at 3:50 PM Xueming Li <xuemingl@mellanox.com> wrote:
>
> When resize a memory with next element, the original element size grows.
> If the orginal element has padding, the real inner element size didn't
> grow as well and this causes trailer verification failure when malloc
> debug enabled.
I did not see this when running the malloc_autotest with debug enabled.
What is missing for me to catch it?
Just a bit chilly to apply this series.
The first patch seems an optimisation.
The second one seems more interesting if we fix the debug mode, but I
suppose we can live without them in 19.11.
--
David Marchand
next prev parent reply other threads:[~2019-11-19 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 14:50 [dpdk-dev] [PATCH 1/2] malloc: fix realloc wrong copy size Xueming Li
2019-11-12 14:50 ` [dpdk-dev] [PATCH 2/2] malloc: fix realloc padded element size Xueming Li
2019-11-14 15:11 ` Burakov, Anatoly
2019-11-19 20:47 ` David Marchand [this message]
2019-11-20 2:12 ` [dpdk-dev] [dpdk-stable] " Xueming(Steven) Li
2019-11-20 13:25 ` David Marchand
2019-11-21 12:30 ` Burakov, Anatoly
2019-11-21 12:55 ` Xueming(Steven) Li
2019-11-21 13:15 ` Burakov, Anatoly
2019-11-21 13:17 ` Burakov, Anatoly
2019-11-21 14:11 ` Xueming(Steven) Li
2019-11-14 15:11 ` [dpdk-dev] [PATCH 1/2] malloc: fix realloc wrong copy size Burakov, Anatoly
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='CAJFAV8xieOuFRQpBQhOERUqS7372774H=qk9eO4iy86ku79fpQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=xuemingl@mellanox.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).