From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master] BUILD REGRESSION cb153b68ff91cbc434f3de70ac549e110543e1bb
Date: Fri, 11 Mar 2022 18:40:10 +0800 [thread overview]
Message-ID: <e56d93b3-1bc7-9fa3-dc95-61b23f37530f@intel.com> (raw)
In-Reply-To: <dd6f8f11-8158-1b6b-00ce-b664f5451e77@oracle.com>
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 <lkp@intel.com> 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
prev parent reply other threads:[~2022-03-11 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 21:14 kernel test robot
2022-03-09 22:04 ` Andrew Morton
2022-03-09 22:45 ` Mike Kravetz
2022-03-11 10:40 ` Chen, Rong A [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e56d93b3-1bc7-9fa3-dc95-61b23f37530f@intel.com \
--to=rong.a.chen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mike.kravetz@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox