From: kernel test robot <lkp@intel.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: [linux-next:master 8922/11208] lib/x86_64/processor.c:636:25: error: 'KVM_X86_XCOMP_GUEST_SUPP' undeclared
Date: Tue, 19 Jul 2022 09:28:51 +0800 [thread overview]
Message-ID: <202207190951.yMvCFx3C-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 036ad6daa8f0fd357af7f50f9da58539eaa6f68c
commit: 3bb267a36185b64949ea9c8bbfe93eb01986f6cb [8922/11208] selftests: drop khdr make target
reproduce: make O=/tmp/kselftest -C tools/testing/selftests
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 036ad6daa8f0fd357af7f50f9da58539eaa6f68c builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
lib/x86_64/processor.c: In function 'vm_xsave_req_perm':
>> lib/x86_64/processor.c:636:25: error: 'KVM_X86_XCOMP_GUEST_SUPP' undeclared (first use in this function)
636 | .attr = KVM_X86_XCOMP_GUEST_SUPP,
| ^~~~~~~~~~~~~~~~~~~~~~~~
lib/x86_64/processor.c:636:25: note: each undeclared identifier is reported only once for each function it appears in
>> lib/x86_64/processor.c:652:38: error: 'ARCH_REQ_XCOMP_GUEST_PERM' undeclared (first use in this function); did you mean 'ARCH_REQ_XCOMP_PERM'?
652 | rc = syscall(SYS_arch_prctl, ARCH_REQ_XCOMP_GUEST_PERM, bit);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| ARCH_REQ_XCOMP_PERM
>> lib/x86_64/processor.c:661:38: error: 'ARCH_GET_XCOMP_GUEST_PERM' undeclared (first use in this function); did you mean 'ARCH_GET_XCOMP_PERM'?
661 | rc = syscall(SYS_arch_prctl, ARCH_GET_XCOMP_GUEST_PERM, &bitmask);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| ARCH_GET_XCOMP_PERM
lib/x86_64/processor.c: In function 'vcpu_save_xsave_state':
>> lib/x86_64/processor.c:1085:33: error: 'KVM_CAP_XSAVE2' undeclared (first use in this function); did you mean 'KVM_CAP_XSAVE'?
1085 | size = vm_check_cap(vm, KVM_CAP_XSAVE2);
| ^~~~~~~~~~~~~~
| KVM_CAP_XSAVE
lib/x86_64/processor.c:1093:40: error: 'KVM_GET_XSAVE2' undeclared (first use in this function); did you mean 'KVM_GET_XSAVE'?
1093 | return ioctl(vcpu->fd, KVM_GET_XSAVE2, state->xsave);
| ^~~~~~~~~~~~~~
| KVM_GET_XSAVE
lib/x86_64/processor.c:1094:1: warning: control reaches end of non-void function [-Wreturn-type]
1094 | }
| ^
--
fs_test.c: In function 'layout1_file_and_dir_access_rights_child':
>> fs_test.c:404:21: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
404 | #define ACCESS_LAST LANDLOCK_ACCESS_FS_REFER
| ^~~~~~~~~~~~~~~~~~~~~~~~
fs_test.c:418:9: note: in expansion of macro 'ACCESS_LAST'
418 | ACCESS_LAST)
| ^~~~~~~~~~~
fs_test.c:429:38: note: in expansion of macro 'ACCESS_ALL'
429 | .handled_access_fs = ACCESS_ALL,
| ^~~~~~~~~~
fs_test.c:404:21: note: each undeclared identifier is reported only once for each function it appears in
404 | #define ACCESS_LAST LANDLOCK_ACCESS_FS_REFER
| ^~~~~~~~~~~~~~~~~~~~~~~~
fs_test.c:418:9: note: in expansion of macro 'ACCESS_LAST'
418 | ACCESS_LAST)
| ^~~~~~~~~~~
fs_test.c:429:38: note: in expansion of macro 'ACCESS_ALL'
429 | .handled_access_fs = ACCESS_ALL,
| ^~~~~~~~~~
fs_test.c: In function 'layout1_unknown_access_rights_child':
>> fs_test.c:404:21: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
404 | #define ACCESS_LAST LANDLOCK_ACCESS_FS_REFER
| ^~~~~~~~~~~~~~~~~~~~~~~~
fs_test.c:470:55: note: in expansion of macro 'ACCESS_LAST'
470 | for (access_mask = 1ULL << 63; access_mask != ACCESS_LAST;
| ^~~~~~~~~~~
fs_test.c: In function 'layout1_reparent_refer_child':
fs_test.c:1980:35: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
1980 | .access = LANDLOCK_ACCESS_FS_REFER,
| ^~~~~~~~~~~~~~~~~~~~~~~~
| LANDLOCK_ACCESS_FS_READ_DIR
fs_test.c: In function 'layout1_reparent_link_child':
fs_test.c:2026:35: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
2026 | .access = LANDLOCK_ACCESS_FS_REFER,
| ^~~~~~~~~~~~~~~~~~~~~~~~
| LANDLOCK_ACCESS_FS_READ_DIR
fs_test.c: In function 'layout1_reparent_rename_child':
fs_test.c:2104:35: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
2104 | .access = LANDLOCK_ACCESS_FS_REFER,
| ^~~~~~~~~~~~~~~~~~~~~~~~
| LANDLOCK_ACCESS_FS_READ_DIR
fs_test.c: In function 'reparent_exdev_layers_enforce1':
fs_test.c:2245:35: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
2245 | .access = LANDLOCK_ACCESS_FS_REFER,
| ^~~~~~~~~~~~~~~~~~~~~~~~
| LANDLOCK_ACCESS_FS_READ_DIR
fs_test.c: In function 'layout1_reparent_remove_child':
fs_test.c:2540:35: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
2540 | .access = LANDLOCK_ACCESS_FS_REFER |
| ^~~~~~~~~~~~~~~~~~~~~~~~
| LANDLOCK_ACCESS_FS_READ_DIR
fs_test.c: In function 'layout1_reparent_dom_superset_child':
fs_test.c:2602:35: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
2602 | .access = LANDLOCK_ACCESS_FS_REFER,
| ^~~~~~~~~~~~~~~~~~~~~~~~
| LANDLOCK_ACCESS_FS_READ_DIR
fs_test.c: In function 'layout1_bind_reparent_cross_mount_child':
fs_test.c:3244:35: error: 'LANDLOCK_ACCESS_FS_REFER' undeclared (first use in this function); did you mean 'LANDLOCK_ACCESS_FS_READ_DIR'?
3244 | .access = LANDLOCK_ACCESS_FS_REFER,
| ^~~~~~~~~~~~~~~~~~~~~~~~
| LANDLOCK_ACCESS_FS_READ_DIR
--
pm_nl_ctl.c: In function 'capture_events':
>> pm_nl_ctl.c:189:61: error: 'MPTCP_ATTR_SERVER_SIDE' undeclared (first use in this function); did you mean 'MPTCP_ATTR_REM_ID'?
189 | else if (attrs->rta_type == MPTCP_ATTR_SERVER_SIDE)
| ^~~~~~~~~~~~~~~~~~~~~~
| MPTCP_ATTR_REM_ID
pm_nl_ctl.c:189:61: note: each undeclared identifier is reported only once for each function it appears in
pm_nl_ctl.c: In function 'dsf':
>> pm_nl_ctl.c:347:46: error: 'MPTCP_PM_CMD_SUBFLOW_DESTROY' undeclared (first use in this function)
347 | off = init_genl_req(data, pm_family, MPTCP_PM_CMD_SUBFLOW_DESTROY,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> pm_nl_ctl.c:391:60: error: 'MPTCP_PM_ATTR_ADDR_REMOTE' undeclared (first use in this function); did you mean 'MPTCP_PM_ATTR_ADDR'?
391 | ((arg == 0) ? MPTCP_PM_ATTR_ADDR : MPTCP_PM_ATTR_ADDR_REMOTE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| MPTCP_PM_ATTR_ADDR
>> pm_nl_ctl.c:430:25: error: 'MPTCP_PM_ATTR_TOKEN' undeclared (first use in this function); did you mean 'MPTCP_ATTR_TOKEN'?
430 | rta->rta_type = MPTCP_PM_ATTR_TOKEN;
| ^~~~~~~~~~~~~~~~~~~
| MPTCP_ATTR_TOKEN
pm_nl_ctl.c: In function 'csf':
>> pm_nl_ctl.c:461:46: error: 'MPTCP_PM_CMD_SUBFLOW_CREATE' undeclared (first use in this function)
461 | off = init_genl_req(data, pm_family, MPTCP_PM_CMD_SUBFLOW_CREATE,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
pm_nl_ctl.c:505:60: error: 'MPTCP_PM_ATTR_ADDR_REMOTE' undeclared (first use in this function); did you mean 'MPTCP_PM_ATTR_ADDR'?
505 | ((arg == 0) ? MPTCP_PM_ATTR_ADDR : MPTCP_PM_ATTR_ADDR_REMOTE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| MPTCP_PM_ATTR_ADDR
pm_nl_ctl.c:556:25: error: 'MPTCP_PM_ATTR_TOKEN' undeclared (first use in this function); did you mean 'MPTCP_ATTR_TOKEN'?
556 | rta->rta_type = MPTCP_PM_ATTR_TOKEN;
| ^~~~~~~~~~~~~~~~~~~
| MPTCP_ATTR_TOKEN
pm_nl_ctl.c: In function 'remove_addr':
>> pm_nl_ctl.c:580:46: error: 'MPTCP_PM_CMD_REMOVE' undeclared (first use in this function); did you mean 'MPTCP_PM_CMD_UNSPEC'?
580 | off = init_genl_req(data, pm_family, MPTCP_PM_CMD_REMOVE,
| ^~~~~~~~~~~~~~~~~~~
| MPTCP_PM_CMD_UNSPEC
>> pm_nl_ctl.c:593:41: error: 'MPTCP_PM_ATTR_LOC_ID' undeclared (first use in this function); did you mean 'MPTCP_ATTR_LOC_ID'?
593 | rta->rta_type = MPTCP_PM_ATTR_LOC_ID;
| ^~~~~~~~~~~~~~~~~~~~
| MPTCP_ATTR_LOC_ID
pm_nl_ctl.c:603:41: error: 'MPTCP_PM_ATTR_TOKEN' undeclared (first use in this function); did you mean 'MPTCP_ATTR_TOKEN'?
603 | rta->rta_type = MPTCP_PM_ATTR_TOKEN;
| ^~~~~~~~~~~~~~~~~~~
| MPTCP_ATTR_TOKEN
pm_nl_ctl.c: In function 'announce_addr':
>> pm_nl_ctl.c:632:46: error: 'MPTCP_PM_CMD_ANNOUNCE' undeclared (first use in this function); did you mean 'MPTCP_PM_CMD_UNSPEC'?
632 | off = init_genl_req(data, pm_family, MPTCP_PM_CMD_ANNOUNCE,
| ^~~~~~~~~~~~~~~~~~~~~
| MPTCP_PM_CMD_UNSPEC
pm_nl_ctl.c:732:25: error: 'MPTCP_PM_ATTR_TOKEN' undeclared (first use in this function); did you mean 'MPTCP_ATTR_TOKEN'?
732 | rta->rta_type = MPTCP_PM_ATTR_TOKEN;
| ^~~~~~~~~~~~~~~~~~~
| MPTCP_ATTR_TOKEN
pm_nl_ctl.c: In function 'print_addr':
>> pm_nl_ctl.c:1008:37: error: 'MPTCP_PM_ADDR_FLAG_IMPLICIT' undeclared (first use in this function); did you mean 'MPTCP_PM_ADDR_FLAG_FULLMESH'?
1008 | if (flags & MPTCP_PM_ADDR_FLAG_IMPLICIT) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
| MPTCP_PM_ADDR_FLAG_FULLMESH
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-19 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 1:28 kernel test robot [this message]
2022-07-19 7:49 ` Guillaume Tucker
2022-07-20 5:23 ` [kbuild-all] " Chen, Rong A
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=202207190951.yMvCFx3C-lkp@intel.com \
--to=lkp@intel.com \
--cc=guillaume.tucker@collabora.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.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