From: Christian Lamparter <chunkeey@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] crypto: crypto4xx - Call dma_unmap_page when done
Date: Wed, 8 Feb 2023 20:03:37 +0100 [thread overview]
Message-ID: <cf60caa6-a540-c09a-e34b-4fdf30fd0d39@gmail.com> (raw)
In-Reply-To: <Y+CX0WWNtrURdr5g@gondor.apana.org.au>
On 2/6/23 07:01, Herbert Xu wrote:
> In crypto4xx_cipher_done, we should be unmapping the dst page, not
> mapping it.
>
> This was flagged by a sparse warning about the unused addr variable.
> While we're at it, also fix a sparse warning regarding the unused
> ctx variable in crypto4xx_ahash_done (by actually using it).
>
> Fixes: 049359d65527 ("crypto: amcc - Add crypt4xx driver")
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Tested this on the MyBook Live. Internal cryptmgr_test pass with:
[ 2.888784] alg: No test for stdrng (crypto4xx_rng)
[ 7.519740] "cryptomgr_test" (102) uses obsolete ecb(arc4) skcipher
(but all crypto4xx entries in /proc/crypto say that the selftest pass)
as well as libkcapi kcapi-enc-test.sh passes.
The ahash portion is a bit "underused". Currently the driver doesn't
register any hashes (this is because in testing I found the getting
the crypto-hardware to do those is so much slower than letting the
CPU do these).
Anyway:
Tested-by: Christian Lamparter <chunkeey@gmail.com>
Thanks!
prev parent reply other threads:[~2023-02-08 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 6:01 [PATCH] crypto: crypto4xx - Call dma_unmap_page when done Herbert Xu
2023-02-08 19:03 ` Christian Lamparter [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=cf60caa6-a540-c09a-e34b-4fdf30fd0d39@gmail.com \
--to=chunkeey@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.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 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.