From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [weiny2:tip-pks-v4.10-5.12-rc 9/17] arch/x86/entry/common.c:328:3: error: implicit declaration of function 'pkrs_restore_irq'; did you mean
Date: Fri, 19 Mar 2021 19:55:18 +0800 [thread overview]
Message-ID: <202103191913.LZPbArk0-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]
tree: https://github.com/weiny2/linux-kernel.git tip-pks-v4.10-5.12-rc
head: 74e4f6716199c0b1af6e647582a6b83c4a38cd2d
commit: fdc7d4ec8c2b4ad63e037502fd15407c204a1642 [9/17] x86/entry: Preserve PKRS MSR across exceptions
config: x86_64-rhel-7.6-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/weiny2/linux-kernel/commit/fdc7d4ec8c2b4ad63e037502fd15407c204a1642
git remote add weiny2 https://github.com/weiny2/linux-kernel.git
git fetch --no-tags weiny2 tip-pks-v4.10-5.12-rc
git checkout fdc7d4ec8c2b4ad63e037502fd15407c204a1642
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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/entry/common.c:200:24: warning: no previous prototype for 'do_SYSENTER_32' [-Wmissing-prototypes]
200 | __visible noinstr long do_SYSENTER_32(struct pt_regs *regs)
| ^~~~~~~~~~~~~~
arch/x86/entry/common.c:318:24: warning: no previous prototype for 'xen_pv_evtchn_do_upcall' [-Wmissing-prototypes]
318 | __visible noinstr void xen_pv_evtchn_do_upcall(struct pt_regs *regs)
| ^~~~~~~~~~~~~~~~~~~~~~~
arch/x86/entry/common.c: In function 'xen_pv_evtchn_do_upcall':
>> arch/x86/entry/common.c:328:3: error: implicit declaration of function 'pkrs_restore_irq'; did you mean 'xa_store_irq'? [-Werror=implicit-function-declaration]
328 | pkrs_restore_irq(regs);
| ^~~~~~~~~~~~~~~~
| xa_store_irq
cc1: some warnings being treated as errors
vim +328 arch/x86/entry/common.c
317
318 __visible noinstr void xen_pv_evtchn_do_upcall(struct pt_regs *regs)
319 {
320 irqentry_state_t state = irqentry_enter(regs);
321 bool inhcall;
322
323 run_sysvec_on_irqstack_cond(__xen_pv_evtchn_do_upcall, regs);
324
325 inhcall = get_and_clear_inhcall();
326 if (inhcall && !WARN_ON_ONCE(state.exit_rcu)) {
327 /* Normally called by irqentry_exit, we must restore pkrs here */
> 328 pkrs_restore_irq(regs);
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 50659 bytes --]
reply other threads:[~2021-03-19 11:55 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=202103191913.LZPbArk0-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.