From: sashiko-bot@kernel.org
To: "Chenghai Huang" <huangchenghai2@huawei.com>,
herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, liulongfang@huawei.com,
qianweili@huawei.com, wangzhou1@hisilicon.com,
linwenkai6@hisilicon.com
Subject: Re: [PATCH 2/4] crypto: engine - add acomp support
Date: Mon, 09 Nov 2026 07:46:49 +0000 [thread overview]
Message-ID: <sashiko-outbox-204552@kernel.org> (raw)
In-Reply-To: <20261109073556.2517351-3-huangchenghai2@huawei.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] crypto: engine - missing CRYPTO_ACOMP select in CRYPTO_ENGINE
Kconfig
--
commit 21d47c711df84337042460c8075ae29a58a54c22
Author: Chenghai Huang <huangchenghai2@huawei.com>
crypto: engine - add acomp support
This commit adds asynchronous compression (acomp) request transfer,
finalization, and algorithm registration helpers to the crypto engine
framework, and moves struct acomp_alg to include/crypto/acompress.h.
> diff --git a/crypto/crypto_engine.c b/crypto/crypto_engine.c
> index 5b669038acb45..2a0740d9dd634 100644
> --- a/crypto/crypto_engine.c
> +++ b/crypto/crypto_engine.c
[ ... ]
> @@ -504,6 +532,20 @@ void crypto_engine_exit(struct crypto_engine *engine)
> }
> EXPORT_SYMBOL_GPL(crypto_engine_exit);
>
> +int crypto_engine_register_acomp(struct acomp_engine_alg *alg)
> +{
> + if (!alg->op.do_one_request)
> + return -EINVAL;
> + return crypto_register_acomp(&alg->base);
> +}
> +EXPORT_SYMBOL_GPL(crypto_engine_register_acomp);
> +
> +void crypto_engine_unregister_acomp(struct acomp_engine_alg *alg)
> +{
> + crypto_unregister_acomp(&alg->base);
> +}
> +EXPORT_SYMBOL_GPL(crypto_engine_unregister_acomp);
> +
> int crypto_engine_register_aead(struct aead_engine_alg *alg)
> {
> if (!alg->op.do_one_request)
[Severity: High]
Does CRYPTO_ENGINE in crypto/Kconfig also need to select CRYPTO_ACOMP?
crypto_register_acomp() and crypto_unregister_acomp() are only built when
CONFIG_CRYPTO_ACOMP2 is enabled, and have no inline stub fallbacks.
Unlike CRYPTO_AEAD, CRYPTO_AKCIPHER, CRYPTO_HASH, CRYPTO_KPP, and
CRYPTO_SKCIPHER, CRYPTO_ENGINE does not select CRYPTO_ACOMP, so enabling
CONFIG_CRYPTO_ENGINE without CONFIG_CRYPTO_ACOMP2 (or with
CONFIG_CRYPTO_ENGINE=y and CONFIG_CRYPTO_ACOMP2=m) fails to link with
undefined references to crypto_register_acomp() and
crypto_unregister_acomp().
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109073556.2517351-1-huangchenghai2@huawei.com?part=2
next prev parent reply other threads:[~2026-11-09 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 7:35 [PATCH 0/4] crypto: engine - add acomp support and adapt Hisilicon HPRE and ZIP drivers Chenghai Huang
2026-11-09 7:35 ` [PATCH 1/4] crypto: engine - clear busy and recheck running in the retry pump loop Chenghai Huang
2026-11-12 9:06 ` Jean-Michel Hautbois
2026-11-09 7:35 ` [PATCH 2/4] crypto: engine - add acomp support Chenghai Huang
2026-11-09 7:46 ` sashiko-bot [this message]
2026-11-09 22:17 ` kernel test robot
2026-11-10 2:05 ` kernel test robot
2026-11-09 7:35 ` [PATCH 3/4] crypto: hisilicon/hpre - use crypto engine framework Chenghai Huang
2026-11-09 8:00 ` sashiko-bot
2026-11-09 7:35 ` [PATCH 4/4] crypto: hisilicon/zip - adapt to use crypto engine Chenghai Huang
2026-11-09 8:05 ` sashiko-bot
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=sashiko-outbox-204552@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=huangchenghai2@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linwenkai6@hisilicon.com \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wangzhou1@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.