From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 02BACD5C0; Tue, 8 May 2018 17:53:38 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2018 08:53:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,379,1520924400"; d="scan'208";a="37768292" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga007.fm.intel.com with ESMTP; 08 May 2018 08:53:35 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.150]) by IRSMSX104.ger.corp.intel.com ([169.254.5.96]) with mapi id 14.03.0319.002; Tue, 8 May 2018 16:53:17 +0100 From: "De Lara Guarch, Pablo" To: "Zhang, Roy Fan" CC: "dev@dpdk.org" , "stable@dpdk.org" Thread-Topic: [PATCH 2/2] crypto/scheduler: fix memory leak Thread-Index: AQHT3XCdJpJxnwgRk0eHb2ew4MFQfqQlyTgAgABFOoA= Date: Tue, 8 May 2018 15:53:16 +0000 Message-ID: References: <20180426150950.7568-1-pablo.de.lara.guarch@intel.com> <20180426150950.7568-2-pablo.de.lara.guarch@intel.com> <9F7182E3F746AB4EA17801C148F3C604332283C2@IRSMSX102.ger.corp.intel.com> In-Reply-To: <9F7182E3F746AB4EA17801C148F3C604332283C2@IRSMSX102.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzg0NzUzMjYtY2NhYS00MDYxLTkyZWEtMGY0ZTRhOGFjYTRjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6Im9nQ1pJamxpMFlUZkNINzlSdDZFNnRsZlhNRTd1dk9vUzFxcmhlSzdDSlU9In0= x-ctpclassification: CTP_NT 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 15:53:39 -0000 > -----Original Message----- > From: Zhang, Roy Fan > Sent: Tuesday, May 8, 2018 1:45 PM > To: De Lara Guarch, Pablo > Cc: dev@dpdk.org; stable@dpdk.org > Subject: RE: [PATCH 2/2] crypto/scheduler: fix memory leak >=20 >=20 >=20 > > -----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 > > > > If private context creation fails, the memory allocated for it and for > > some of the rings created was being leaked. > > In case of failure, it must be freed. > > > > Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling > > mode") > > Cc: stable@dpdk.org > > > > Signed-off-by: Pablo de Lara > > >=20 > Acked-by: Fan Zhang Applied to dpdk-next-crypto. Pablo