From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: [peterz-queue:x86/wip.ibt 7/15] arch/x86/kernel/setup.c:65:1: warning: 'nocf_check' attribute ignored; use -fcf-protection to enable the attribute
Date: Sat, 15 Jan 2022 15:31:19 +0800 [thread overview]
Message-ID: <202201151505.wRwvYlwh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/wip.ibt
head: 7b31f08c5f3fb5f3cfd75deb24787569f35315d5
commit: e4b4623dc6a99968ab59ea14cdae2c7a09924838 [7/15] x86: Don't generate ENDBR in .discard.text
config: x86_64-randconfig-a003 (https://download.01.org/0day-ci/archive/20220115/202201151505.wRwvYlwh-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 82c8aca93488730ce8f66101e0f3538f14b551dd)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=e4b4623dc6a99968ab59ea14cdae2c7a09924838
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 e4b4623dc6a99968ab59ea14cdae2c7a09924838
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/kernel/ arch/x86/mm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/setup.c:65:1: warning: 'nocf_check' attribute ignored; use -fcf-protection to enable the attribute [-Wignored-attributes]
RESERVE_BRK(dmi_alloc, 65536);
^
arch/x86/include/asm/setup.h:122:56: note: expanded from macro 'RESERVE_BRK'
static void __section(".discard.text") __attribute__((nocf_check)) __used notrace \
^
1 warning generated.
--
>> arch/x86/mm/init.c:178:1: warning: 'nocf_check' attribute ignored; use -fcf-protection to enable the attribute [-Wignored-attributes]
RESERVE_BRK(early_pgt_alloc, INIT_PGT_BUF_SIZE);
^
arch/x86/include/asm/setup.h:122:56: note: expanded from macro 'RESERVE_BRK'
static void __section(".discard.text") __attribute__((nocf_check)) __used notrace \
^
1 warning generated.
vim +/nocf_check +65 arch/x86/kernel/setup.c
2b72394e408964 Pekka Enberg 2009-04-28 63
e808bae2407a08 Thadeu Lima de Souza Cascardo 2010-02-09 64 #ifdef CONFIG_DMI
796216a57fe45c Jeremy Fitzhardinge 2009-03-12 @65 RESERVE_BRK(dmi_alloc, 65536);
e808bae2407a08 Thadeu Lima de Souza Cascardo 2010-02-09 66 #endif
796216a57fe45c Jeremy Fitzhardinge 2009-03-12 67
c0b5842a457d44 Ingo Molnar 2009-01-27 68
:::::: The code at line 65 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-01-15 7:32 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=202201151505.wRwvYlwh-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).