From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] crypto: arm64/aes-ccm - Rewrite skcipher walker loop
Date: Wed, 1 Feb 2023 17:15:23 +0800 [thread overview]
Message-ID: <477c73bd-b56e-3c63-1ad6-6a2a08af42af@linux.alibaba.com> (raw)
In-Reply-To: <Y9opEyTFKXAVjk/D@gondor.apana.org.au>
Hi Herbert,
On 2/1/23 4:55 PM, Herbert Xu wrote:
> On Wed, Feb 01, 2023 at 10:53:37AM +0800, Tianjia Zhang wrote:
>>
>> while (walk.nbytes != walk.total) {
>
> This is still buggy, because we can have walk.nbytes == 0 and
> walk.nbytes != walk.total. You will enter the loop and call
> skcipher_walk_done which is not allowed.
>
> That is why you should follow the standard calling convention
> for skcipher walks, always check for walk.nbytes != 0 and not
> whether the walk returns an error.
>
> Cheers,
According to your previous reply, walker will ensure that the nbytes of
each iteration is at least the size of the chunk. If walk.nbytes == 0,
it must be the last chunk. If this is the case,
walk.nbytes == 0 && walk.nbytes != walk.total will not appear, sorry I
am not very clear about the details of walker, I don’t know if I
understand correctly.
Cheers,
Tianjia
next prev parent reply other threads:[~2023-02-01 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 8:58 [PATCH] crypto: arm64/aes-ccm - Rewrite skcipher walker loop Herbert Xu
2023-01-30 10:42 ` Ard Biesheuvel
2023-01-31 3:19 ` Herbert Xu
2023-02-01 2:53 ` Tianjia Zhang
2023-02-01 8:55 ` Herbert Xu
2023-02-01 9:15 ` Tianjia Zhang [this message]
2023-02-01 9:21 ` Herbert Xu
2023-02-01 9:43 ` Tianjia Zhang
2023-02-01 9:50 ` Herbert Xu
2023-02-01 9:54 ` Tianjia Zhang
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=477c73bd-b56e-3c63-1ad6-6a2a08af42af@linux.alibaba.com \
--to=tianjia.zhang@linux.alibaba.com \
--cc=ardb@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox