From: "Bo Liu (刘波)-浪潮信息" <liubo03@inspur.com>
To: "hsiangkao@linux.alibaba.com" <hsiangkao@linux.alibaba.com>,
"xiang@kernel.org" <xiang@kernel.org>,
"chao@kernel.org" <chao@kernel.org>
Cc: "linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] erofs: fix build error with CONFIG_EROFS_FS_ZIP_ACCEL=y
Date: Thu, 17 Jul 2025 05:36:07 +0000 [thread overview]
Message-ID: <d850ca30f0fd4c54a2ff66c984571565@inspur.com> (raw)
In-Reply-To: <c46f71ae-f04c-4aa6-99fb-cf8f8e751589@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
>On 2025/7/17 09:58, Bo Liu wrote:
>> fix build err:
>> 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
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes:
>> https://lore.kernel.org/oe-kbuild-all/202507161032.QholMPtn-lkp@intel.
>> com/
>> Fixes: b4a29efc5146 ("erofs: support DEFLATE decompression by using
>> Intel QAT")
>> Signed-off-by: Bo Liu <liubo03@inspur.com>
>>
>> v1:
>> https://lore.kernel.org/linux-erofs/7a1dbee70a604583bae5a29f690f4231@i
>> nspur.com/T/#t
>>
>> change since v1:
>> - add Fixes commits
>> ---
>> fs/erofs/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/fs/erofs/Kconfig b/fs/erofs/Kconfig index
>> 6beeb7063871..60510a041bf1 100644
>> --- a/fs/erofs/Kconfig
>> +++ b/fs/erofs/Kconfig
>> @@ -147,6 +147,7 @@ config EROFS_FS_ZIP_ZSTD
>> config EROFS_FS_ZIP_ACCEL
>> bool "EROFS hardware decompression support"
>> depends on EROFS_FS_ZIP
>> + select CRYPTO
>
>After testing, I think we should rely on CRYPTO_ACOMP or CRYPTO_ACOMP2
>instead.
>
>Otherwise it will still fails.
I will change it.
Thanks.
Bo Liu.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3925 bytes --]
prev parent reply other threads:[~2025-07-17 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 1:58 Bo Liu
2025-07-17 2:45 ` Gao Xiang
2025-07-17 5:36 ` Bo Liu (刘波)-浪潮信息 [this message]
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=d850ca30f0fd4c54a2ff66c984571565@inspur.com \
--to=liubo03@inspur.com \
--cc=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--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®