From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0FEE8C433EF for ; Fri, 11 Mar 2022 10:40:20 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 51BAF8D0002; Fri, 11 Mar 2022 05:40:20 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 4CB728D0001; Fri, 11 Mar 2022 05:40:20 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3E0848D0002; Fri, 11 Mar 2022 05:40:20 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.25]) by kanga.kvack.org (Postfix) with ESMTP id 2D86B8D0001 for ; Fri, 11 Mar 2022 05:40:20 -0500 (EST) Received: from smtpin14.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id DE64922BC for ; Fri, 11 Mar 2022 10:40:19 +0000 (UTC) X-FDA: 79231760958.14.F4EE979 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by imf10.hostedemail.com (Postfix) with ESMTP id F2070C0012 for ; Fri, 11 Mar 2022 10:40:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646995219; x=1678531219; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=YJSfpg5bwQRLm4oaT+l4syukdQTC03ngTDKEP6HcPsU=; b=La9aDqlbiEB5txt5XCR3wu8RB+/L9Y5nAA5xFHPofYoDf5XXN9BgsPMZ Y+GvGH4GI/TZmz1UnWKLghUe474dyecGvZBcMod8N152aN4yvRzxZFWS5 cLH1Gb8ZBiQGyCeRh0CkQle50+xolkep/L2yTRfFN5JsS+0Ajdr2EcVGz yg7svLJfPcF3QwODtmxgAdgQalD2vrCt0pqoXnHhSeOeCYQsAVtP7Fwbb VFfRL/f/dJxr6QE9eNscJqBddT5Uohp1h3ub7ykZ597r57+5SAJACl1WT WvjgfigfpRNTxWJkLOLdrF2Mx6I/RI2iOVMz3LuFnt2daC2diZhqG4jel w==; X-IronPort-AV: E=McAfee;i="6200,9189,10282"; a="254376864" X-IronPort-AV: E=Sophos;i="5.90,173,1643702400"; d="scan'208";a="254376864" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Mar 2022 02:40:14 -0800 X-IronPort-AV: E=Sophos;i="5.90,173,1643702400"; d="scan'208";a="555255706" Received: from rongch2-mobl.ccr.corp.intel.com (HELO [10.255.28.251]) ([10.255.28.251]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Mar 2022 02:40:13 -0800 Subject: Re: [linux-next:master] BUILD REGRESSION cb153b68ff91cbc434f3de70ac549e110543e1bb To: Mike Kravetz , Andrew Morton , kernel test robot Cc: Linux Memory Management List References: <6227c724.wu0h617RqdUJmtL1%lkp@intel.com> <20220309140446.7e803050736f1096c7a1e133@linux-foundation.org> From: "Chen, Rong A" Message-ID: Date: Fri, 11 Mar 2022 18:40:10 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: F2070C0012 X-Stat-Signature: jqhqyhxf634y61c6bf861dgq7mskoqpn Authentication-Results: imf10.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=La9aDqlb; spf=none (imf10.hostedemail.com: domain of rong.a.chen@intel.com has no SPF policy when checking 192.55.52.120) smtp.mailfrom=rong.a.chen@intel.com; dmarc=pass (policy=none) header.from=intel.com X-Rspam-User: X-Rspamd-Server: rspam06 X-HE-Tag: 1646995218-547509 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 3/10/2022 6:45 AM, Mike Kravetz wrote: > On 3/9/22 14:04, Andrew Morton wrote: >> On Wed, 09 Mar 2022 05:14:12 +0800 kernel test robot wrote: >> >>> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master >>> branch HEAD: cb153b68ff91cbc434f3de70ac549e110543e1bb Add linux-next specific files for 20220308 >>> >>> ... >>> >>> mm/hugetlb.c:4170 hugepages_setup() warn: potential spectre issue 'default_hugepages_in_node' [w] >>> mm/hugetlb.c:4172 hugepages_setup() warn: potential spectre issue 'parsed_hstate->max_huge_pages_node' [w] >> >> Thanks. >> >> "hugetlb: clean up potential spectre issue warnings" was supposed to >> fix these. >> >> https://ozlabs.org/~akpm/mmotm/broken-out/hugetlb-clean-up-potential-spectre-issue-warnings.patch >> https://ozlabs.org/~akpm/mmotm/broken-out/hugetlb-clean-up-potential-spectre-issue-warnings-v2.patch >> >> Are they present in your tree? > > When I took a quick look yesterday, those line numbers (4170 and 4172) did not > seem correct. They appeared to be from a version of hugetlb.c without the > above referenced change. However, branch HEAD: cb153b68ff91 does contain the > referenced change. ??? > Hi, Sorry for the inconvenience, this is a known defect in the summary report, we don't have enough resource to confirm the errors whether fixed or not in latest branch, so the errors here were discovered recently, we'll update the description in the report to avoid noise. Best Regards, Rong Chen