From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-kernel@vger.kernel.org
Subject: [djwong-xfs:vectorized-scrub 110/308] ld.lld: error: undefined symbol: xchk_iscan_start
Date: Sun, 17 Oct 2021 16:46:07 +0800 [thread overview]
Message-ID: <202110171600.32WFMyu4-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2723 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git vectorized-scrub
head: d404c6b945070ba14d8db1ee79daa5df149877df
commit: aa567553268823bd23b665100da66740bfab460a [110/308] xfs: online repair of parent pointers
config: i386-randconfig-a011-20211016 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 8ca4b3ef19fe82d7ad6a6e1515317dcc01b41515)
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/djwong/xfs-linux.git/commit/?id=aa567553268823bd23b665100da66740bfab460a
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs vectorized-scrub
git checkout aa567553268823bd23b665100da66740bfab460a
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 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.lld: error: undefined symbol: xchk_iscan_start
>>> referenced by parent_repair.c:294 (fs/xfs/scrub/parent_repair.c:294)
>>> xfs/scrub/parent_repair.o:(xrep_parent_scan) in archive fs/built-in.a
--
>> ld.lld: error: undefined symbol: xchk_iscan_advance
>>> referenced by parent_repair.c:295 (fs/xfs/scrub/parent_repair.c:295)
>>> xfs/scrub/parent_repair.o:(xrep_parent_scan) in archive fs/built-in.a
>>> referenced by parent_repair.c:295 (fs/xfs/scrub/parent_repair.c:295)
>>> xfs/scrub/parent_repair.o:(xrep_parent_scan) in archive fs/built-in.a
--
>> ld.lld: error: undefined symbol: xchk_iscan_iget
>>> referenced by parent_repair.c:296 (fs/xfs/scrub/parent_repair.c:296)
>>> xfs/scrub/parent_repair.o:(xrep_parent_scan) in archive fs/built-in.a
--
>> ld.lld: error: undefined symbol: __xchk_iscan_visit
>>> referenced by iscan.h:76 (fs/xfs/scrub/iscan.h:76)
>>> xfs/scrub/parent_repair.o:(xrep_parent_scan) in archive fs/built-in.a
--
>> ld.lld: error: undefined symbol: xchk_iscan_finish
>>> referenced by parent_repair.c:314 (fs/xfs/scrub/parent_repair.c:314)
>>> xfs/scrub/parent_repair.o:(xrep_parent_scan) in archive fs/built-in.a
>>> referenced by parent_repair.c:314 (fs/xfs/scrub/parent_repair.c:314)
>>> xfs/scrub/parent_repair.o:(xrep_parent_scan) in archive fs/built-in.a
---
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: 35099 bytes --]
reply other threads:[~2021-10-17 8:46 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=202110171600.32WFMyu4-lkp@intel.com \
--to=lkp@intel.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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®