From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 6825B8DA6; Tue, 8 May 2018 14:45:29 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2018 05:45:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,378,1520924400"; d="scan'208";a="226738942" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by fmsmga005.fm.intel.com with ESMTP; 08 May 2018 05:45:26 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.249]) by IRSMSX101.ger.corp.intel.com ([169.254.1.118]) with mapi id 14.03.0319.002; Tue, 8 May 2018 13:45:25 +0100 From: "Zhang, Roy Fan" To: "De Lara Guarch, Pablo" CC: "dev@dpdk.org" , "stable@dpdk.org" Thread-Topic: [PATCH 2/2] crypto/scheduler: fix memory leak Thread-Index: AQHT3XCddGo6CpaA1k6jI2fw1fDqz6Ql2dgA Date: Tue, 8 May 2018 12:45:24 +0000 Message-ID: <9F7182E3F746AB4EA17801C148F3C604332283C2@IRSMSX102.ger.corp.intel.com> References: <20180426150950.7568-1-pablo.de.lara.guarch@intel.com> <20180426150950.7568-2-pablo.de.lara.guarch@intel.com> In-Reply-To: <20180426150950.7568-2-pablo.de.lara.guarch@intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzg0NzUzMjYtY2NhYS00MDYxLTkyZWEtMGY0ZTRhOGFjYTRjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJjdjZzNzY1Q1A2TkpvYUNKZkR2TktcL29MbnVBaHRkVERicnNJcFYwQW91RDB0aTYrY1llSHpKS01SdFY4eVZSTSJ9 dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 2/2] crypto/scheduler: fix memory 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: Tue, 08 May 2018 12:45:30 -0000 > -----Original Message----- > From: De Lara Guarch, Pablo > Sent: Thursday, April 26, 2018 4:10 PM > To: Zhang, Roy Fan > Cc: dev@dpdk.org; De Lara Guarch, Pablo ; > stable@dpdk.org > Subject: [PATCH 2/2] crypto/scheduler: fix memory leak >=20 > If private context creation fails, the memory allocated for it and for so= me of > the rings created was being leaked. > In case of failure, it must be freed. >=20 > Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling mode") > Cc: stable@dpdk.org >=20 > Signed-off-by: Pablo de Lara > Acked-by: Fan Zhang