DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Legacy, Allain (Wind River)" <allain.legacy@windriver.com>,
	"Osman, Dahir (Wind River)" <dahir.osman@windriver.com>
Cc: dev@dpdk.org, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] ip_frag: free mbufs on reassembly table destroy
Date: Thu, 22 Jun 2017 17:56:29 +0200	[thread overview]
Message-ID: <1918941.YOME2ufcob@xps> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772583FB05ED1@IRSMSX109.ger.corp.intel.com>

> > 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>

Applied, thanks

      reply	other threads:[~2017-06-22 15:56 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
2017-06-22 15:56     ` Thomas Monjalon [this message]

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=1918941.YOME2ufcob@xps \
    --to=thomas@monjalon.net \
    --cc=allain.legacy@windriver.com \
    --cc=dahir.osman@windriver.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).