From: kernel test robot <lkp@intel.com>
To: Kai Huang <kai.huang@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, kvm@vger.kernel.org,
Farrah Chen <farrah.chen@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [kvm:kvm-coco-queue-20250129 43/129] include/linux/init.h:319:27: error: redefinition of '__exitcall_vt_exit'
Date: Fri, 31 Jan 2025 21:43:23 +0800 [thread overview]
Message-ID: <202501312122.IIuMSJu4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-coco-queue-20250129
head: 0bc4f452607db4e7eee4d3056cd6ec98636260bc
commit: 4b55a8f7c5f508fe1dd0005aecc81bbb5676aaec [43/129] KVM: VMX: Refactor VMX module init/exit functions
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20250131/202501312122.IIuMSJu4-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501312122.IIuMSJu4-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501312122.IIuMSJu4-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/moduleparam.h:5,
from arch/x86/kvm/vmx/main.c:2:
arch/x86/kvm/vmx/main.c:176:13: error: 'vt_exit' undeclared here (not in a function); did you mean 'vmx_exit'?
176 | module_exit(vt_exit);
| ^~~~~~~
include/linux/init.h:319:57: note: in definition of macro '__exitcall'
319 | static exitcall_t __exitcall_##fn __exit_call = fn
| ^~
arch/x86/kvm/vmx/main.c:176:1: note: in expansion of macro 'module_exit'
176 | module_exit(vt_exit);
| ^~~~~~~~~~~
>> include/linux/init.h:319:27: error: redefinition of '__exitcall_vt_exit'
319 | static exitcall_t __exitcall_##fn __exit_call = fn
| ^~~~~~~~~~~
include/linux/module.h:100:25: note: in expansion of macro '__exitcall'
100 | #define module_exit(x) __exitcall(x);
| ^~~~~~~~~~
arch/x86/kvm/vmx/main.c:183:1: note: in expansion of macro 'module_exit'
183 | module_exit(vt_exit);
| ^~~~~~~~~~~
include/linux/init.h:319:27: note: previous definition of '__exitcall_vt_exit' with type 'exitcall_t' {aka 'void (*)(void)'}
319 | static exitcall_t __exitcall_##fn __exit_call = fn
| ^~~~~~~~~~~
include/linux/module.h:100:25: note: in expansion of macro '__exitcall'
100 | #define module_exit(x) __exitcall(x);
| ^~~~~~~~~~
arch/x86/kvm/vmx/main.c:176:1: note: in expansion of macro 'module_exit'
176 | module_exit(vt_exit);
| ^~~~~~~~~~~
vim +/__exitcall_vt_exit +319 include/linux/init.h
^1da177e4c3f41 Linus Torvalds 2005-04-16 317
^1da177e4c3f41 Linus Torvalds 2005-04-16 318 #define __exitcall(fn) \
^1da177e4c3f41 Linus Torvalds 2005-04-16 @319 static exitcall_t __exitcall_##fn __exit_call = fn
^1da177e4c3f41 Linus Torvalds 2005-04-16 320
:::::: The code at line 319 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-31 13:44 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=202501312122.IIuMSJu4-lkp@intel.com \
--to=lkp@intel.com \
--cc=farrah.chen@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
/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.