From: kernel test robot <lkp@intel.com>
To: Bo Liu <liubo03@inspur.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Gao Xiang <xiang@kernel.org>
Subject: ld.lld: error: undefined symbol: crypto_req_done
Date: Wed, 16 Jul 2025 10:56:20 +0800 [thread overview]
Message-ID: <202507161032.QholMPtn-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 155a3c003e555a7300d156a5252c004c392ec6b0
commit: b4a29efc51461edf1a02e9da656d4480cabd24b0 erofs: support DEFLATE decompression by using Intel QAT
date: 7 weeks ago
config: mips-randconfig-r054-20250716 (https://download.01.org/0day-ci/archive/20250716/202507161032.QholMPtn-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 16534d19bf50bde879a83f0ae62875e2c5120e64)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250716/202507161032.QholMPtn-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/202507161032.QholMPtn-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: crypto_req_done
>>> referenced by decompressor_crypto.c
>>> fs/erofs/decompressor_crypto.o:(z_erofs_crypto_decompress) in archive vmlinux.a
>>> referenced by decompressor_crypto.c
>>> fs/erofs/decompressor_crypto.o:(z_erofs_crypto_decompress) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: crypto_acomp_decompress
>>> referenced by decompressor_crypto.c
>>> fs/erofs/decompressor_crypto.o:(z_erofs_crypto_decompress) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: crypto_alloc_acomp
>>> referenced by decompressor_crypto.c
>>> fs/erofs/decompressor_crypto.o:(z_erofs_crypto_enable_engine) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-16 2:57 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=202507161032.QholMPtn-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xiang@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®