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:43:00 +0800 [thread overview]
Message-ID: <7fdf700c-6747-fa58-ee7a-2cca6397fa05@linux.alibaba.com> (raw)
In-Reply-To: <Y9ovNyYP03rUBPlq@gondor.apana.org.au>
Hi Herbert,
On 2/1/23 5:21 PM, Herbert Xu wrote:
> On Wed, Feb 01, 2023 at 05:15:23PM +0800, Tianjia Zhang wrote:
>>
>> 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,
>
> walk.nbytes == 0 is used to indicate error. Of course you could
> check for an error return in addition to checking walk.nbytes but
> that's how this bug got created in the first place.
>
> So always check for walk.nbytes == 0.
>
> Cheers,
It seems that only need to fix the loop condition, so if change the
loop condition of the code just now to
while (walk.nbytes && walk.nbytes != walk.total), in this way, the
last chunk cryption is separated out of the loop, which will be clearer
logically. What is your opinion?
Thanks,
Tianjia
next prev parent reply other threads:[~2023-02-01 9:44 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
2023-02-01 9:21 ` Herbert Xu
2023-02-01 9:43 ` Tianjia Zhang [this message]
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=7fdf700c-6747-fa58-ee7a-2cca6397fa05@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