From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 0B05CA05D3 for ; Thu, 25 Apr 2019 08:09:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id F00A01B560; Thu, 25 Apr 2019 08:09:33 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id ADA911B554; Thu, 25 Apr 2019 08:09:31 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2019 23:09:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,392,1549958400"; d="scan'208";a="153584602" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga002.jf.intel.com with ESMTP; 24 Apr 2019 23:09:30 -0700 Received: from fmsmsx158.amr.corp.intel.com (10.18.116.75) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 24 Apr 2019 23:09:29 -0700 Received: from hasmsx114.ger.corp.intel.com (10.184.198.65) by fmsmsx158.amr.corp.intel.com (10.18.116.75) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 24 Apr 2019 23:09:30 -0700 Received: from hasmsx105.ger.corp.intel.com ([169.254.1.47]) by HASMSX114.ger.corp.intel.com ([169.254.14.177]) with mapi id 14.03.0415.000; Thu, 25 Apr 2019 09:08:31 +0300 From: "Stojaczyk, Dariusz" To: "Lipiec, Herakliusz" CC: "dev@dpdk.org" , "Lipiec, Herakliusz" , "jianfeng.tan@intel.com" , "stable@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v2 3/8] ipc: fix vdev memleak Thread-Index: AQHU+fwzM9Ga3sq01EeI+qrzsNhAT6ZMZnTg Date: Thu, 25 Apr 2019 06:08:29 +0000 Message-ID: References: <20190417143822.21276-1-herakliusz.lipiec@intel.com> <20190423174334.19612-1-herakliusz.lipiec@intel.com> <20190423174334.19612-4-herakliusz.lipiec@intel.com> In-Reply-To: <20190423174334.19612-4-herakliusz.lipiec@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-originating-ip: [10.102.11.37] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2 3/8] ipc: fix vdev memleak 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190425060829.-jXQGbzx4BcW2f-CXGdhTSZK6UQX39oiwa_DNOHm_Lk@z> > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Herakliusz Lipiec > Sent: Tuesday, April 23, 2019 7:43 PM > Cc: dev@dpdk.org; Lipiec, Herakliusz ; > jianfeng.tan@intel.com; stable@dpdk.org > Subject: [dpdk-dev] [PATCH v2 3/8] ipc: fix vdev memleak >=20 > When sending synchronous IPC requests, the caller must free the response > buffer even if the request returned failure. Fix the code to correctly > use the IPC API. >=20 > Bugzilla ID: 228 > Fixes: cdb068f031c6 ("bus/vdev: scan by multi-process channel") > Cc: jianfeng.tan@intel.com > Cc: stable@dpdk.org > Signed-off-by: Herakliusz Lipiec > --- Reviewed-by: Darek Stojaczyk Thanks!