From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [peterz-queue:x86/module 3/5] module.c:undefined reference to `split_lock_enabled'
Date: Mon, 25 May 2020 08:59:50 +0800 [thread overview]
Message-ID: <202005250847.WfoiVAEN%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/module
head: 3c6c41559b25f20eac2ba492ce596335f060ad0f
commit: 039bc206dab1e5d1844f7ddfd774f7b3fef7f4b5 [3/5] x86,module: Detect VMX vs SLD conflicts
config: um-defconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
git checkout 039bc206dab1e5d1844f7ddfd774f7b3fef7f4b5
# save the attached .config to linux build tree
make W=1 ARCH=um
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
/usr/bin/ld: arch/x86/um/../kernel/module.o: in function `decode_module':
>> module.c:(.text+0x25): undefined reference to `split_lock_enabled'
>> /usr/bin/ld: module.c:(.text+0x37): undefined reference to `insn_init'
>> /usr/bin/ld: module.c:(.text+0x69): undefined reference to `insn_get_length'
>> /usr/bin/ld: module.c:(.text+0x14e): undefined reference to `insn_get_prefixes'
collect2: error: ld returned 1 exit status
---
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: 8485 bytes --]
next reply other threads:[~2020-05-25 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 0:59 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-26 22:51 [peterz-queue:x86/module 3/5] module.c:undefined reference to `split_lock_enabled' kernel test robot
2021-02-21 13:14 kernel test robot
2020-06-20 0:19 kernel test robot
2020-06-10 1:53 kernel test robot
2020-05-15 21:18 kbuild test robot
2020-05-08 19:32 kbuild test robot
2020-04-27 21:21 kbuild test robot
2020-04-20 10:08 kbuild test robot
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=202005250847.WfoiVAEN%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.