From: kbuild test robot <fengguang.wu@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: [tip:WIP.x86/pti 1/1] arch/x86/mm/cpu_entry_area.c:153:33: error: 'CPU_ENTRY_AREA_END' undeclared; did you mean 'CPU_ENTRY_AREA_BASE'?
Date: Sun, 24 Dec 2017 03:04:51 +0800 [thread overview]
Message-ID: <201712240347.5x9Cd697%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/pti
head: 1c4c1c2fa0c5c121210d47bc74ee85c5032b3ea9
commit: 1c4c1c2fa0c5c121210d47bc74ee85c5032b3ea9 [1/1] x86/pti: Prevent wraparound in setup_cpu_entry_area_ptes() on 32bit
config: i386-randconfig-x007-201752 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
git checkout 1c4c1c2fa0c5c121210d47bc74ee85c5032b3ea9
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
arch/x86/mm/cpu_entry_area.c: In function 'setup_cpu_entry_area_ptes':
>> arch/x86/mm/cpu_entry_area.c:153:33: error: 'CPU_ENTRY_AREA_END' undeclared (first use in this function); did you mean 'CPU_ENTRY_AREA_BASE'?
for (; start < end && start >= CPU_ENTRY_AREA_END; start += PMD_SIZE)
^~~~~~~~~~~~~~~~~~
CPU_ENTRY_AREA_BASE
arch/x86/mm/cpu_entry_area.c:153:33: note: each undeclared identifier is reported only once for each function it appears in
vim +153 arch/x86/mm/cpu_entry_area.c
140
141 static __init void setup_cpu_entry_area_ptes(void)
142 {
143 #ifdef CONFIG_X86_32
144 unsigned long start, end;
145
146 BUILD_BUG_ON(CPU_ENTRY_AREA_PAGES * PAGE_SIZE < CPU_ENTRY_AREA_MAP_SIZE);
147 BUG_ON(CPU_ENTRY_AREA_BASE & ~PMD_MASK);
148
149 start = CPU_ENTRY_AREA_BASE;
150 end = start + CPU_ENTRY_AREA_MAP_SIZE;
151
152 /* Careful here: start + PMD_SIZE might wrap around */
> 153 for (; start < end && start >= CPU_ENTRY_AREA_END; start += PMD_SIZE)
154 populate_extra_pte(start);
155 #endif
156 }
157
---
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: 26305 bytes --]
reply other threads:[~2017-12-23 19:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201712240347.5x9Cd697%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.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
all inboxes | Powered by JetHome®