From: kbuild test robot <lkp@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Dave Hansen <dave.hansen@linux.intel.com>,
mceier@gmail.com, aaro.koskinen@nokia.com, aarcange@redhat.com,
luto@kernel.org, arjan@linux.intel.com, bp@alien8.de,
dan.j.williams@intel.com, dwmw2@infradead.org,
gregkh@linuxfoundation.org, hughd@google.com,
jpoimboe@redhat.com, jgross@suse.com, keescook@google.com,
torvalds@linux-foundation.org, namit@vmware.com,
peterz@infradead.org, tglx@linutronix.de
Subject: Re: [PATCH 2/2] x86, pti: fix boot warning from Global-bit setting
Date: Wed, 18 Apr 2018 20:26:00 +0800 [thread overview]
Message-ID: <201804182048.QIJW9gCy%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180417211304.7B3F1FDB@viggo.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
Hi Dave,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.17-rc1 next-20180418]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Dave-Hansen/x86-pti-fix-boot-problems-from-Global-bit-setting/20180418-181719
config: i386-randconfig-a0-201815 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
arch/x86/mm/pageattr.c: In function '__cpa_pfn_in_highmap':
arch/x86/mm/pageattr.c:1161:2: error: implicit declaration of function 'highmap_start_pfn' [-Werror=implicit-function-declaration]
return within_inclusive(pfn, highmap_start_pfn(),
^
>> arch/x86/mm/pageattr.c:1162:4: error: implicit declaration of function 'highmap_end_pfn' [-Werror=implicit-function-declaration]
highmap_end_pfn());
^
cc1: some warnings being treated as errors
vim +/highmap_end_pfn +1162 arch/x86/mm/pageattr.c
1154
1155 bool __cpa_pfn_in_highmap(unsigned long pfn)
1156 {
1157 /*
1158 * Kernel text has an alias mapping at a high address, known
1159 * here as "highmap".
1160 */
> 1161 return within_inclusive(pfn, highmap_start_pfn(),
> 1162 highmap_end_pfn());
1163 }
1164
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30973 bytes --]
next prev parent reply other threads:[~2018-04-18 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:13 [PATCH 1/2] x86, pti: fix boot problems from Global-bit setting Dave Hansen
2018-04-17 21:13 ` [PATCH 2/2] x86, pti: fix boot warning " Dave Hansen
2018-04-17 21:56 ` Mariusz Ceier
2018-04-18 11:05 ` kbuild test robot
2018-04-18 12:26 ` kbuild test robot [this message]
2018-04-20 10:16 ` Thomas Gleixner
2018-04-20 19:44 ` Dave Hansen
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=201804182048.QIJW9gCy%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aarcange@redhat.com \
--cc=aaro.koskinen@nokia.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@01.org \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mceier@gmail.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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