All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Dror Birkman <dror.birkman@lightcyber.com>
Cc: nicolas.pernas.maradei@emutex.com, ferruh.yigit@intel.com,
	dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] pcap: fix memory leak in jumbo frames
Date: Tue, 20 Sep 2016 18:58:29 +0800	[thread overview]
Message-ID: <20160920105829.GU23158@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1474367963-83879-1-git-send-email-dror.birkman@lightcyber.com>

On Tue, Sep 20, 2016 at 01:39:23PM +0300, Dror Birkman wrote:
> If rte_pktmbuf_alloc() fails on any segment that is not the initial
> segment, previously allocated mbufs are not freed.

You should put a "fixline" here.

Besides that, I think it's a good candidate for stable branch. Thus,
stable@dpdk.org cc'ed.

	--yliu

  reply	other threads:[~2016-09-20 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 10:39 [PATCH] pcap: fix memory leak in jumbo frames Dror Birkman
2016-09-20 10:58 ` Yuanhan Liu [this message]
2016-09-20 11:16   ` Dror Birkman
2016-09-20 11:57     ` [dpdk-stable] " Yuanhan Liu

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=20160920105829.GU23158@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.