From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org, reshma.pattan@intel.com
Cc: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] reorder: fix ready buffers not being nulled out
Date: Wed, 11 Oct 2017 23:04:59 +0200 [thread overview]
Message-ID: <502598108.IA6mC33nB0@xps> (raw)
In-Reply-To: <1505228764-9738-1-git-send-email-pbhagavatula@caviumnetworks.com>
12/09/2017 17:06, Pavan Nikhilesh:
> The ready buffers should be set to NULL when drained else it might result
> in double free (mempool put) when rte_reorder_free is called.
>
> Fixes: b70b56032bff ("reorder: new library")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Anyone to review, please?
next prev parent reply other threads:[~2017-10-11 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 15:06 Pavan Nikhilesh
2017-09-12 15:06 ` [dpdk-dev] [PATCH 2/2] test/reorder: fix reorder drain test Pavan Nikhilesh
2017-10-12 8:28 ` Bruce Richardson
2017-10-11 21:04 ` Thomas Monjalon [this message]
2017-10-12 8:32 ` [dpdk-dev] [PATCH 1/2] reorder: fix ready buffers not being nulled out Bruce Richardson
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=502598108.IA6mC33nB0@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=pbhagavatula@caviumnetworks.com \
--cc=reshma.pattan@intel.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).