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 7/15] arch/x86/kernel/setup.c:66:1: error: 'nocf_check' attribute ignored. Use '-fcf-protection' option to enable it
Date: Mon, 14 Feb 2022 10:47:22 +0800 [thread overview]
Message-ID: <202202141030.qhNGDbYM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/wip.ibt
head: ede73fa4e97e8f275401a989b8d9df192a2c3ec4
commit: 9947fe456516712bd4df7139f2ff329cc14ba745 [7/15] x86: Don't generate ENDBR in .discard.text
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220214/202202141030.qhNGDbYM-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=9947fe456516712bd4df7139f2ff329cc14ba745
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 9947fe456516712bd4df7139f2ff329cc14ba745
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
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 >>):
>> arch/x86/kernel/setup.c:66:1: error: 'nocf_check' attribute ignored. Use '-fcf-protection' option to enable it [-Werror=attributes]
66 | RESERVE_BRK(dmi_alloc, 65536);
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
--
>> arch/x86/mm/init.c:178:1: error: 'nocf_check' attribute ignored. Use '-fcf-protection' option to enable it [-Werror=attributes]
178 | RESERVE_BRK(early_pgt_alloc, INIT_PGT_BUF_SIZE);
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
vim +66 arch/x86/kernel/setup.c
2b72394e408964 Pekka Enberg 2009-04-28 64
e808bae2407a08 Thadeu Lima de Souza Cascardo 2010-02-09 65 #ifdef CONFIG_DMI
796216a57fe45c Jeremy Fitzhardinge 2009-03-12 @66 RESERVE_BRK(dmi_alloc, 65536);
e808bae2407a08 Thadeu Lima de Souza Cascardo 2010-02-09 67 #endif
796216a57fe45c Jeremy Fitzhardinge 2009-03-12 68
c0b5842a457d44 Ingo Molnar 2009-01-27 69
:::::: The code at line 66 was first introduced by commit
:::::: 796216a57fe45c04adc35bda1f0782efec78a713 x86: allow extend_brk users to reserve brk space
:::::: TO: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
:::::: CC: H. Peter Anvin <hpa@zytor.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-14 2:48 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=202202141030.qhNGDbYM-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
all inboxes | Powered by JetHome®