From: kernel test robot <lkp@intel.com>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Anuj Gupta <anuj20.g@samsung.com>
Subject: [axboe-block:nvme-passthru-wip.2 15/23] exit.c:(.text+0xac0): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
Date: Wed, 22 Dec 2021 08:07:53 +0800 [thread overview]
Message-ID: <202112220837.r55Kf9nN-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git nvme-passthru-wip.2
head: 7567defdb3c6a81e4114a03ddf3d6c158df81a76
commit: bc18161c9b80cf2d647710257f9716ee6c66fee4 [15/23] io_uring: add flag and helper for fixed-buffer uring-cmd
config: nds32-randconfig-r032-20211220 (https://download.01.org/0day-ci/archive/20211222/202112220837.r55Kf9nN-lkp@intel.com/config)
compiler: nds32le-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=bc18161c9b80cf2d647710257f9716ee6c66fee4
git remote add axboe-block https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
git fetch --no-tags axboe-block nvme-passthru-wip.2
git checkout bc18161c9b80cf2d647710257f9716ee6c66fee4
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 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 >>):
nds32le-linux-ld: kernel/exit.o: in function `io_uring_cmd_import_fixed':
>> exit.c:(.text+0xac0): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: fs/exec.o: in function `io_uring_cmd_import_fixed':
exec.c:(.text+0x19c0): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: block/fops.o: in function `io_uring_cmd_import_fixed':
fops.c:(.text+0x1480): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: drivers/nvme/host/core.o: in function `io_uring_cmd_import_fixed':
core.c:(.text+0x2d00): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: drivers/nvme/host/ioctl.o: in function `io_uring_cmd_import_fixed':
ioctl.c:(.text+0x980): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: drivers/nvme/host/multipath.o: in function `io_uring_cmd_import_fixed':
multipath.c:(.text+0xa00): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: drivers/nvme/host/fabrics.o: in function `io_uring_cmd_import_fixed':
fabrics.c:(.text+0xb40): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: drivers/nvme/host/fc.o: in function `io_uring_cmd_import_fixed':
fc.c:(.text+0x4740): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: drivers/nvme/target/passthru.o: in function `io_uring_cmd_import_fixed':
passthru.c:(.text+0x780): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
nds32le-linux-ld: drivers/nvme/target/fcloop.o: in function `io_uring_cmd_import_fixed':
fcloop.c:(.text+0x2240): multiple definition of `io_uring_cmd_import_fixed'; kernel/fork.o:fork.c:(.text+0x600): first defined here
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-22 0:08 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=202112220837.r55Kf9nN-lkp@intel.com \
--to=lkp@intel.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=joshi.k@samsung.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®