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: arch/x86/kernel/traps.c:248:17: error: implicit declaration of function '__warn'; did you mean 'pr_warn'?
Date: Mon, 18 Apr 2022 05:45:36 +0800 [thread overview]
Message-ID: <202204180524.7PXohDtU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a1901b464e7e3e28956ae7423db2847dbbfb5be8
commit: 991625f3dd2cbc4b787deb0213e2bcf8fa264b21 x86/ibt: Add IBT feature, MSR and #CP handling
date: 5 weeks ago
config: x86_64-buildonly-randconfig-r006-20220418 (https://download.01.org/0day-ci/archive/20220418/202204180524.7PXohDtU-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=991625f3dd2cbc4b787deb0213e2bcf8fa264b21
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 991625f3dd2cbc4b787deb0213e2bcf8fa264b21
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 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/traps.c: In function '__exc_control_protection':
>> arch/x86/kernel/traps.c:248:17: error: implicit declaration of function '__warn'; did you mean 'pr_warn'? [-Werror=implicit-function-declaration]
248 | __warn(__FILE__, __LINE__, (void *)regs->ip, TAINT_WARN, regs, NULL);
| ^~~~~~
| pr_warn
cc1: some warnings being treated as errors
vim +248 arch/x86/kernel/traps.c
229
230 DEFINE_IDTENTRY_ERRORCODE(exc_control_protection)
231 {
232 if (!cpu_feature_enabled(X86_FEATURE_IBT)) {
233 pr_err("Unexpected #CP\n");
234 BUG();
235 }
236
237 if (WARN_ON_ONCE(user_mode(regs) || (error_code & CP_EC) != CP_ENDBR))
238 return;
239
240 if (unlikely(regs->ip == (unsigned long)&ibt_selftest_ip)) {
241 regs->ax = 0;
242 return;
243 }
244
245 pr_err("Missing ENDBR: %pS\n", (void *)instruction_pointer(regs));
246 if (!ibt_fatal) {
247 printk(KERN_DEFAULT CUT_HERE);
> 248 __warn(__FILE__, __LINE__, (void *)regs->ip, TAINT_WARN, regs, NULL);
249 return;
250 }
251 BUG();
252 }
253
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-17 21:46 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=202204180524.7PXohDtU-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®