From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Subject: [chao:bugfix/syzbot 40/42] ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
Date: Tue, 7 May 2024 06:08:22 +0800 [thread overview]
Message-ID: <202405070648.GAPbgYby-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot
head: 6fd891b7248d0b825dbff6454be21f60c7ba1fb0
commit: 28a4fc03f837d64c67eeeba5ef226dbed4b369dc [40/42] f2fs: check validation of fault attrs in f2fs_build_fault_attr()
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240507/202405070648.GAPbgYby-lkp@intel.com/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240507/202405070648.GAPbgYby-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/202405070648.GAPbgYby-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at iostat.c
>>> fs/f2fs/iostat.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at extent_cache.c
>>> fs/f2fs/extent_cache.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at shrinker.c
>>> fs/f2fs/shrinker.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at recovery.c
>>> fs/f2fs/recovery.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at segment.c
>>> fs/f2fs/segment.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at node.c
>>> fs/f2fs/node.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at acl.c
>>> fs/f2fs/acl.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at xattr.c
>>> fs/f2fs/xattr.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at debug.c
>>> fs/f2fs/debug.o:(.text+0x0)
--
>> ld.lld: error: duplicate symbol: __pfx_f2fs_build_fault_attr
>>> defined at dir.c
>>> fs/f2fs/dir.o:(__pfx_f2fs_build_fault_attr)
>>> defined at sysfs.c
>>> fs/f2fs/sysfs.o:(.text+0x0)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-06 22: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=202405070648.GAPbgYby-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yuchao0@huawei.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).