From: David Marchand <david.marchand@redhat.com>
To: Volodymyr Fialko <vfialko@marvell.com>
Cc: dev@dpdk.org, Reshma Pattan <reshma.pattan@intel.com>,
David Hunt <david.hunt@intel.com>,
jerinj@marvell.com, anoobj@marvell.com, ci@dpdk.org
Subject: Re: [PATCH 2/2] test/reorder: fix double free of drained buffers
Date: Thu, 26 Jan 2023 16:51:37 +0100 [thread overview]
Message-ID: <CAJFAV8xwQzTUC3F4C=z5Pk-m5KPOQn81j=BsuUSjJYyqDUS2=Q@mail.gmail.com> (raw)
In-Reply-To: <20230107151939.2540148-3-vfialko@marvell.com>
On Sat, Jan 7, 2023 at 4:20 PM Volodymyr Fialko <vfialko@marvell.com> wrote:
>
> Set to zero array of drained buffers after free, to prevent freeing them
> one more time.
> Discovered with enabled `RTE_LIBRTE_MEMPOOL_DEBUG`.
Good catch, having those debug options enabled in the CI could be interesting.
Cc: CI people, for info.
--
David Marchand
parent reply other threads:[~2023-01-26 15:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230107151939.2540148-3-vfialko@marvell.com>]
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='CAJFAV8xwQzTUC3F4C=z5Pk-m5KPOQn81j=BsuUSjJYyqDUS2=Q@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anoobj@marvell.com \
--cc=ci@dpdk.org \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=reshma.pattan@intel.com \
--cc=vfialko@marvell.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).