From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id A0AE91BB8A for ; Thu, 10 May 2018 18:03:17 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2018 09:03:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,385,1520924400"; d="scan'208";a="54807352" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga001.jf.intel.com with ESMTP; 10 May 2018 09:03:15 -0700 Received: from irsmsx112.ger.corp.intel.com (10.108.20.5) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 10 May 2018 17:03:15 +0100 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.214]) by irsmsx112.ger.corp.intel.com ([169.254.1.237]) with mapi id 14.03.0319.002; Thu, 10 May 2018 17:03:14 +0100 From: "Ananyev, Konstantin" To: "Burakov, Anatoly" , "dev@dpdk.org" CC: "Liu, Yong" , "Burakov, Anatoly" Thread-Topic: [dpdk-dev] [PATCH 2/3] memalloc: fix wrong return value on freeing segment on fail Thread-Index: AQHT4scnXd0Lb7hxZk6pfHZC7421bqQpKx7g Date: Thu, 10 May 2018 16:03:14 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258AEDC56A2@irsmsx105.ger.corp.intel.com> References: <556d606e3af8ab32e920611d166a0154e472fe25.1525342009.git.anatoly.burakov@intel.com> In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZWY1OTZjZTctN2M3NC00ODUxLTkyMjctZjQxMzQxYzJmMThiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IkNvOWlidW9MTE9MVFoxellURWR1OEVKbWhUWitHUDFWNnZXVkRaRVpFNFU9In0= 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/3] memalloc: fix wrong return value on freeing segment on fail 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: Thu, 10 May 2018 16:03:18 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anatoly Burakov > Sent: Thursday, May 3, 2018 11:11 AM > To: dev@dpdk.org > Cc: Liu, Yong ; Burakov, Anatoly > Subject: [dpdk-dev] [PATCH 2/3] memalloc: fix wrong return value on freei= ng segment on fail >=20 > Return value should be zero for success, but if unlock and unlink > have succeeded, return value was 1, which triggered failure message > in calling code. >=20 > Fixes: a5ff05d60fc5 ("mem: support unmapping pages at runtime") > Cc: anatoly.burakov@intel.com >=20 > Signed-off-by: Anatoly Burakov > --- Acked-by: Konstantin Ananyev