From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Bo Liu <liubo03@inspur.com>, xiang@kernel.org, chao@kernel.org
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] erofs: fix build error with CONFIG_EROFS_FS_ZIP_ACCEL=y
Date: Fri, 18 Jul 2025 15:18:48 +0800 [thread overview]
Message-ID: <3134e79d-9f91-4af5-a15c-ab65509bef55@linux.alibaba.com> (raw)
In-Reply-To: <20250718033039.3609-1-liubo03@inspur.com>
On 2025/7/18 11:30, 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>
Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>
> change since v3:
> - change Kconfg to select CRYPTO and CRYPTO_DEFLATE
These two lines should be moved under the line `----`, since
it shouldn't be part of the commit message, but I've removed
this time.
Thanks,
Gao Xiang
prev parent reply other threads:[~2025-07-18 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 3:30 Bo Liu
2025-07-18 7:18 ` Gao Xiang [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=3134e79d-9f91-4af5-a15c-ab65509bef55@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
--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®