From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] pdump: fix possible mbuf leak Date: Sun, 12 Nov 2017 04:13:00 +0100 Message-ID: <2402132.7maDu73vrK@xps> References: <20171110135516.23996-1-matvejchikov@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, reshma.pattan@intel.com To: "Ilya V. Matveychikov" Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id B36121B28F for ; Sun, 12 Nov 2017 07:58:56 +0100 (CET) In-Reply-To: <20171110135516.23996-1-matvejchikov@gmail.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 10/11/2017 14:55, Ilya V. Matveychikov: > If pdump_pktmbuf_copy_data() fails it's possible to have segment leak > as rte_pktmbuf_free() only handles m_dup chain but not the seg just > allocated and yet not chained. > > Fixes: 278f945402c5 ("pdump: add new library for packet capture") > Cc: reshma.pattan@intel.com > > Signed-off-by: Ilya V. Matveychikov Applied, thanks