From: Herbert Xu <herbert@gondor.apana.org.au>
To: Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, davem@davemloft.net,
hannes@cmpxchg.org, linux-crypto@vger.kernel.org,
linux-mm@kvack.org, nphamcs@gmail.com, yosryahmed@google.com,
zhouchengming@bytedance.com, chriscli@google.com,
chrisl@kernel.org, ddstreet@ieee.org,
linux-kernel@vger.kernel.org, sjenning@redhat.com,
vitaly.wool@konsulko.com, Barry Song <v-songbaohua@oppo.com>,
Yang Shen <shenyang39@huawei.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: [PATCH v4 1/3] crypto: introduce crypto_acomp_get_alg_flags to expose algorithm flags
Date: Tue, 20 Feb 2024 12:13:34 +0800 [thread overview]
Message-ID: <ZdQm7n6Jc3tqsg1F@gondor.apana.org.au> (raw)
In-Reply-To: <20240220025545.194886-2-21cnbao@gmail.com>
On Tue, Feb 20, 2024 at 03:55:43PM +1300, Barry Song wrote:
>
> diff --git a/drivers/crypto/hisilicon/zip/zip_crypto.c b/drivers/crypto/hisilicon/zip/zip_crypto.c
> index c650c741a18d..94e2d66b04b6 100644
> --- a/drivers/crypto/hisilicon/zip/zip_crypto.c
> +++ b/drivers/crypto/hisilicon/zip/zip_crypto.c
> @@ -591,6 +591,7 @@ static struct acomp_alg hisi_zip_acomp_deflate = {
> .base = {
> .cra_name = "deflate",
> .cra_driver_name = "hisi-deflate-acomp",
> + .cra_flags = CRYPTO_ALG_ASYNC,
> .cra_module = THIS_MODULE,
> .cra_priority = HZIP_ALG_PRIORITY,
> .cra_ctxsize = sizeof(struct hisi_zip_ctx),
> diff --git a/drivers/crypto/intel/iaa/iaa_crypto_main.c b/drivers/crypto/intel/iaa/iaa_crypto_main.c
> index dfd3baf0a8d8..91adf9d76a2e 100644
> --- a/drivers/crypto/intel/iaa/iaa_crypto_main.c
> +++ b/drivers/crypto/intel/iaa/iaa_crypto_main.c
> @@ -1916,6 +1916,7 @@ static struct acomp_alg iaa_acomp_fixed_deflate = {
> .base = {
> .cra_name = "deflate",
> .cra_driver_name = "deflate-iaa",
> + .cra_flags = CRYPTO_ALG_ASYNC,
> .cra_ctxsize = sizeof(struct iaa_compression_ctx),
> .cra_module = THIS_MODULE,
> .cra_priority = IAA_ALG_PRIORITY,
Good catch. I think this should go into a separate bug-fix patch.
> diff --git a/include/crypto/acompress.h b/include/crypto/acompress.h
> index 574cffc90730..07bd8f6bc79a 100644
> --- a/include/crypto/acompress.h
> +++ b/include/crypto/acompress.h
> @@ -160,6 +160,11 @@ static inline void acomp_request_set_tfm(struct acomp_req *req,
> req->base.tfm = crypto_acomp_tfm(tfm);
> }
>
> +static inline u32 crypto_acomp_get_alg_flags(struct crypto_acomp *tfm)
> +{
> + return crypto_tfm_alg_flags(crypto_acomp_tfm(tfm));
> +}
Sorry, my mistake. I shouldn't have suggested copying skcipher
since that gets the tfm flags as opposed to the alg flags which
you've found out.
I think you should just go with your original function acomp_is_async
but do it like this:
static inline bool acomp_is_async(struct crypto_acomp *tfm)
{
return crypto_comp_alg_common(tfm)->base.cra_flags &
CRYPTO_ALG_ASYNC;
}
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2024-02-20 4:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 2:55 [PATCH v4 0/3] mm/zswap & crypto/compress: remove a couple of memcpy Barry Song
2024-02-20 2:55 ` [PATCH v4 1/3] crypto: introduce crypto_acomp_get_alg_flags to expose algorithm flags Barry Song
2024-02-20 4:13 ` Herbert Xu [this message]
2024-02-20 5:05 ` Barry Song
2024-02-20 5:09 ` Herbert Xu
2024-02-20 5:25 ` Barry Song
2024-02-20 2:55 ` [PATCH v4 2/3] mm/zswap: remove the memcpy if acomp is not sleepable Barry Song
2024-02-20 2:55 ` [PATCH v4 3/3] crypto: scompress: remove memcpy if sg_nents is 1 Barry Song
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=ZdQm7n6Jc3tqsg1F@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chriscli@google.com \
--cc=chrisl@kernel.org \
--cc=davem@davemloft.net \
--cc=ddstreet@ieee.org \
--cc=hannes@cmpxchg.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=shenyang39@huawei.com \
--cc=sjenning@redhat.com \
--cc=tom.zanussi@linux.intel.com \
--cc=v-songbaohua@oppo.com \
--cc=vitaly.wool@konsulko.com \
--cc=wangzhou1@hisilicon.com \
--cc=yosryahmed@google.com \
--cc=zhouchengming@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox