From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: cychong <cychong@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ip_frag : Fix double-free of chained mbufs
Date: Fri, 22 Apr 2016 09:54:29 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725836B40B0B@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <1461259681-67118-1-git-send-email-cychong@gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of cychong
> Sent: Thursday, April 21, 2016 6:28 PM
> To: dev@dpdk.org
> Cc: cychong@gmail.com
> Subject: [dpdk-dev] [PATCH] ip_frag : Fix double-free of chained mbufs
>
> If any fragment hole is found in ipv4_frag_reassemble() and ipv6_frag_reassemble(),
> whole ip_frag_pkt mbufs are moved to death-row. Any mbufs already chained to
> another mbuf are freed multiple times as there are still in ip_frag_pkt array.
>
> Signed-off-by: cychong <cychong@gmail.com>
> ---
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
next prev parent reply other threads:[~2016-04-22 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 17:28 cychong
2016-04-22 9:54 ` Ananyev, Konstantin [this message]
2016-04-29 16:04 ` 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=2601191342CEEE43887BDE71AB97725836B40B0B@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=cychong@gmail.com \
--cc=dev@dpdk.org \
/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).