From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Dror Birkman <dror.birkman@lightcyber.com>,
nicolas.pernas.maradei@emutex.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] pcap: fix memory leak in jumbo frames
Date: Wed, 21 Sep 2016 11:57:29 +0100 [thread overview]
Message-ID: <20160921105728.GE16464@bricha3-MOBL3> (raw)
In-Reply-To: <82cb7380-5456-e0f7-ea07-29940f214ac7@intel.com>
On Tue, Sep 20, 2016 at 02:12:38PM +0100, Ferruh Yigit wrote:
> Hi Dror,
>
> On 9/20/2016 1:08 PM, Dror Birkman wrote:
> > If rte_pktmbuf_alloc() fails on any segment that is not the initial
> > segment, previously allocated mbufs are not freed.
> >
> > Fixes: 6db141c91e1f ("pcap: support jumbo frames")
> >
> > Cc: <stable@dpdk.org>
> > Signed-off-by: Dror Birkman <dror.birkman@lightcyber.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
Applied to dpdk-next-net/rel_16_11
/Bruce
prev parent reply other threads:[~2016-09-21 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 12:08 [dpdk-stable] " Dror Birkman
2016-09-20 13:12 ` Ferruh Yigit
2016-09-21 10:57 ` Bruce Richardson [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=20160921105728.GE16464@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dror.birkman@lightcyber.com \
--cc=ferruh.yigit@intel.com \
--cc=nicolas.pernas.maradei@emutex.com \
--cc=stable@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).