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: [peterz-queue:locking/ww_rt_mutex 18/18] ld: kernel/locking/test-ww_rt_mutex.o:(.bss+0x0): multiple definition of `wq'; kernel/locking/test-ww_mutex.o:(.bss+0x0): first defined here
Date: Mon, 19 Jul 2021 08:30:13 +0800 [thread overview]
Message-ID: <202107190807.68NDoKux-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/ww_rt_mutex
head: 401531ec0e4c84f3d26d07d1171f893fee6a08aa
commit: 401531ec0e4c84f3d26d07d1171f893fee6a08aa [18/18] locking/ww_mutex: test_ww_rt_mutex
config: x86_64-randconfig-c022-20210718 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=401531ec0e4c84f3d26d07d1171f893fee6a08aa
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue locking/ww_rt_mutex
git checkout 401531ec0e4c84f3d26d07d1171f893fee6a08aa
# save the attached .config 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 >>):
>> ld: kernel/locking/test-ww_rt_mutex.o:(.bss+0x0): multiple definition of `wq'; kernel/locking/test-ww_mutex.o:(.bss+0x0): first defined here
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37445 bytes --]
reply other threads:[~2021-07-19 0:30 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=202107190807.68NDoKux-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;
as well as URLs for NNTP newsgroup(s).