Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2799874ybl; Thu, 19 Dec 2019 21:48:00 -0800 (PST) X-Google-Smtp-Source: APXvYqymVzB6KA3SfO/IpIk4ymjHO4JhzYnZH4tcZ+LE5sNxL4EzbGAST+/NOXe7O0xRJx9cXlyY X-Received: by 2002:a9d:760f:: with SMTP id k15mr12966936otl.65.1576820880881; Thu, 19 Dec 2019 21:48:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576820880; cv=none; d=google.com; s=arc-20160816; b=KuJlPTZ8LJBq31QS2RoKuQARIbGorGXEuctwIE1U25k+mWdxy2VuG54mgF6nZWTO2D CdlVFsKuCjYR+Y0jqjASfqIT9szK11i6dcMx0N+zlfwm5pDxNu58FwNiXPudeDLp/Hcf +2jKSrQhMZUA3xHkfnbA/jix+ygB6eb8qML7aI127l04lhUIz/7j0bkc/EQQvjRbGF69 x3CHnG7pyqRLJiA0EehkuznvTKpQPyyG/9ANhbbeFgA7cxxiASPRbrQSKXqT79mGOliN JAx/tX9lMz7azEGTd1mG9DFtjgZKLbU0h6g8KhmQrVM/3r9cXNo5xmibf60G1RiCqFio w0xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=l8BWJaz83Zd3weYCzbeyKuMvBhMU+Bcwqu6peb7EydE=; b=KqRv3KOQpz5GUdOCtK6tmN3K+fjLTx1KbcR+h0y8OFPEY9o/Bzq8RgQa2rdOYX1Ouf RSxc9WemzOVVSTP22qcdjNDSGs1ijFfpLd70FMla0QjPwi2UpVKz6L1UADRSfJ9qFfoM 1VDT29X8Kjl0T4bHuJ/1jyuhep6aI2+5/y8QTuGAlHw0ti/bu0ROQyasadaXb2zSNGXR MTkc/5PzY/90MgrCiOdZC8R5Lp7/vZ24kQDzotrJN/BelvYpBv31vRIx4Amcm5jpGgWN xsB1/DzDayLVp1JbAwWBEZN/SoZ3A7521Gpug14HIVJxOCuOMEw42Und1rISRlrGwbt1 SqAQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u16si1679700oia.233.2019.12.19.21.47.46; Thu, 19 Dec 2019 21:48:00 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727165AbfLTFqm (ORCPT + 99 others); Fri, 20 Dec 2019 00:46:42 -0500 Received: from mga09.intel.com ([134.134.136.24]:17673 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725825AbfLTFqm (ORCPT ); Fri, 20 Dec 2019 00:46:42 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2019 21:46:41 -0800 X-IronPort-AV: E=Sophos;i="5.69,334,1571727600"; d="scan'208";a="218719131" Received: from rchatre-mobl.amr.corp.intel.com (HELO [10.251.10.199]) ([10.251.10.199]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Dec 2019 21:46:41 -0800 Subject: Re: [PATCH] x86/resctrl: Fix potential memory leak To: Shakeel Butt Cc: Fenghua Yu , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, LKML References: <20191219223834.233692-1-shakeelb@google.com> <1da649da-6527-d4c2-7d12-40126856ae75@intel.com> From: Reinette Chatre Message-ID: <47f3789b-65cb-172e-ae56-ac8477613a5c@intel.com> Date: Thu, 19 Dec 2019 21:46:40 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Shakeel, On 12/19/2019 5:54 PM, Shakeel Butt wrote: > On Thu, Dec 19, 2019 at 3:27 PM Reinette Chatre > wrote: >> On 12/19/2019 2:38 PM, Shakeel Butt wrote: >>> The set_cache_qos_cfg() is leaking memory when the given level is not >>> RDT_RESOURCE_L3 or RDT_RESOURCE_L2. Fix that. >> >> I think it would be valuable to those considering whether they need to >> backport to know that RDT_RESOURCE_L3 and RDT_RESOURCE_L2 are currently >> the only possible levels with which this function is called. It is thus >> not currently possible for this leak to occur. Indeed a valuable safety >> to add in case this code may change in the future. Thank you very much. >> > > Do you want me to add that info the commit and resend the v2 of the patch? > Yes please. Thank you very much Reinette