From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Legacy, Allain (Wind River)" <allain.legacy@windriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Osman, Dahir (Wind River)" <dahir.osman@windriver.com>
Subject: Re: [dpdk-dev] [PATCH v2] ip_frag: free mbufs on reassembly table destroy
Date: Mon, 5 Jun 2017 22:25:31 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772583FB05ED1@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <20170605154901.110312-1-allain.legacy@windriver.com>
> -----Original Message-----
> From: Allain Legacy [mailto:allain.legacy@windriver.com]
> Sent: Monday, June 5, 2017 4:49 PM
> To: Ananyev, Konstantin <konstantin.ananyev@intel.com>
> Cc: dev@dpdk.org; Osman, Dahir (Wind River) <dahir.osman@windriver.com>
> Subject: [PATCH v2] ip_frag: free mbufs on reassembly table destroy
>
> From: Dahir Osman <dahir.osman@windriver.com>
>
> The rte_ip_frag_table_destroy procedure simply releases the memory for the
> table without freeing the packet buffers that may be referenced in the hash
> table for in-flight or incomplete packet reassembly operations. To prevent
> leaked mbufs go through the list of fragments and free each one
> individually.
>
> Fixes: 416707812c03 ("ip_frag: refactor reassembly code into a proper library")
>
> Reported-by: Matt Peters <matt.peters@windriver.com>
> Signed-off-by: Allain Legacy <allain.legacy@windriver.com>
> ---
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
next prev parent reply other threads:[~2017-06-05 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 17:04 [dpdk-dev] [PATCH] " Allain Legacy
2017-06-04 16:20 ` Ananyev, Konstantin
2017-06-05 14:49 ` Legacy, Allain
2017-06-05 15:49 ` [dpdk-dev] [PATCH v2] " Allain Legacy
2017-06-05 22:25 ` Ananyev, Konstantin [this message]
2017-06-22 15:56 ` 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=2601191342CEEE43887BDE71AB9772583FB05ED1@IRSMSX109.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=allain.legacy@windriver.com \
--cc=dahir.osman@windriver.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).