From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [peterz-queue:x86/wip.ibt 17/47] arch/x86/include/asm/segment.h:278:39: error: 'HAS_KERNEL_IBT' undeclared here (not in a function)
Date: Sat, 26 Feb 2022 19:41:29 +0800 [thread overview]
Message-ID: <202202261948.uPVLnDCm-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/wip.ibt
head: db78c0938593e12efacf2c1821700b6f39754245
commit: 286a983c759d72da5b39c444d8531c7f1135d151 [17/47] x86/ibt,entry: Sprinkle ENDBR dust
config: i386-debian-10.3 (https://download.01.org/0day-ci/archive/20220226/202202261948.uPVLnDCm-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=286a983c759d72da5b39c444d8531c7f1135d151
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue x86/wip.ibt
git checkout 286a983c759d72da5b39c444d8531c7f1135d151
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 prepare
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from arch/x86/include/asm/ptrace.h:5,
from arch/x86/include/asm/math_emu.h:5,
from arch/x86/include/asm/processor.h:13,
from arch/x86/include/asm/cpufeature.h:5,
from arch/x86/include/asm/thread_info.h:53,
from include/linux/thread_info.h:60,
from arch/x86/include/asm/preempt.h:7,
from include/linux/preempt.h:78,
from include/linux/spinlock.h:55,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:6,
from include/linux/slab.h:15,
from include/linux/crypto.h:20,
from arch/x86/kernel/asm-offsets.c:9:
>> arch/x86/include/asm/segment.h:278:39: error: 'HAS_KERNEL_IBT' undeclared here (not in a function)
278 | #define EARLY_IDT_HANDLER_SIZE (9 + 4*HAS_KERNEL_IBT)
| ^~~~~~~~~~~~~~
arch/x86/include/asm/segment.h:290:66: note: in expansion of macro 'EARLY_IDT_HANDLER_SIZE'
290 | extern const char early_idt_handler_array[NUM_EXCEPTION_VECTORS][EARLY_IDT_HANDLER_SIZE];
| ^~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:121: arch/x86/kernel/asm-offsets.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1191: prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:219: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
vim +/HAS_KERNEL_IBT +278 arch/x86/include/asm/segment.h
270
271 /*
272 * early_idt_handler_array is an array of entry points referenced in the
273 * early IDT. For simplicity, it's a real array with one entry point
274 * every nine bytes. That leaves room for an optional 'push $0' if the
275 * vector has no error code (two bytes), a 'push $vector_number' (two
276 * bytes), and a jump to the common entry code (up to five bytes).
277 */
> 278 #define EARLY_IDT_HANDLER_SIZE (9 + 4*HAS_KERNEL_IBT)
279
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-26 11:42 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=202202261948.uPVLnDCm-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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