From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4C11620BB9; Sun, 12 Nov 2017 01:58:56 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 12 Nov 2017 01:58:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=d0G1KDqJ2xTKjmnKsQXrnPyHDu MuWjb/3R0EZue01Z8=; b=J1cTd3PfVJwkNVYG5LaSKeIc8mEry1OhI7/R/riAdA xQixJGeRtPZRr3vuU5flhbSBZKv8K5gTerVhlZOqFRjk/q77kg2wq+lKYyQbH+wj hPtWtpskI4W0Zh4G4uyKqLFt3PYjAKihscxpLe9UHpgz9tCixdfJFnjiyXeD4yVk Y= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=d0G1KD qJ2xTKjmnKsQXrnPyHDuMuWjb/3R0EZue01Z8=; b=KTU/048GNuLwhLSrMF3P47 DX6yGiuN6dzfDcjdqOOs545BFIvOImlAjIosX3QzyPlWCFKvnKcwW7P/FD6VpoDA brB/a92KmDEGp4yWn/SjbfYjxM+RkG8wkQX7Mcnblc9nEZFW/8crCJjmYFIGFWZ5 QJWdvYbASbuAmpCFh0iQE8zjo6VYrvvAc3ELMUZ2J8WMp0EQ0RvJG5Lk6jV21x+X mMe3VF3DuQ7eDmHYX9HiCZM13iJSzVxmGbCMT4g3dcxzqMNwCK1i5vkkdaX+w+KM MDjPQNGbKvSF+4vQkenpF8OTPDdf3DTsMzzni5Nx7qjANv8oVEpGRHIIJJZTGP1w == X-ME-Sender: Received: from xps.localnet (unknown [12.232.154.2]) by mail.messagingengine.com (Postfix) with ESMTPA id CAE0D243F9; Sun, 12 Nov 2017 01:58:55 -0500 (EST) From: Thomas Monjalon To: "Ilya V. Matveychikov" Cc: dev@dpdk.org, reshma.pattan@intel.com Date: Sun, 12 Nov 2017 04:13:00 +0100 Message-ID: <2402132.7maDu73vrK@xps> In-Reply-To: <20171110135516.23996-1-matvejchikov@gmail.com> References: <20171110135516.23996-1-matvejchikov@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] pdump: fix possible mbuf leak X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2017 06:58:57 -0000 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