From: Milan Broz <gmazyland@gmail.com>
To: "Pascal Van Leeuwen" <pvanleeuwen@verimatrix.com>,
"Ondrej Mosnáček" <omosnacek@gmail.com>
Cc: Pascal van Leeuwen <pascalvanl@gmail.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"rsnel@cube.dyndns.org" <rsnel@cube.dyndns.org>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH] crypto: xts - Add support for Cipher Text Stealing
Date: Thu, 8 Aug 2019 06:35:33 +0200 [thread overview]
Message-ID: <fcf6c4b2-b871-6fdc-7803-f94134148299@gmail.com> (raw)
In-Reply-To: <MN2PR20MB297367EE650DBA3308ADD134CAD40@MN2PR20MB2973.namprd20.prod.outlook.com>
Hi,
On 07/08/2019 23:13, Pascal Van Leeuwen wrote:
>> It is a bit confusing, but it is the only reasonable way to support
>> variably sized context and at the same time keep the whole request in
>> a single allocation.
Yes, and the reason here it was detected only for aesni_intel is that
it is submitted though more layers, these depends on variable context length
(at least it run through crypt_simd layer).
I think all other implementations on this 32bit machine were called directly,
so no corruption seen there.
> Ah, ok, I did not know anything about that ... so there's really no way
> I could've done this correctly or to have found the problem myself really.
> Good that it's resolved now, though.
>
> I fixed a couple of other minor things already, is it OK if I roll this
> into an update to my original patch?
Sure, feel free to fold in my change in v2 patch.
I'll test it and provide Tested-by later.
Maybe it would be good to also include /* must be the last */ comment
to the req in struct, though.
Also, maybe this req should have CRYPTO_MINALIGN_ATTR attribute also?
I expect req can be run through exotic hw accelerators later with some
memory alignment requirements. Ondra will know better here, though ;-)
Thanks!
Milan
prev parent reply other threads:[~2019-08-08 4:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 6:55 [PATCH] crypto: xts - Add support for Cipher Text Stealing Pascal van Leeuwen
2019-08-06 18:34 ` Milan Broz
2019-08-06 19:36 ` Pascal Van Leeuwen
2019-08-07 8:15 ` Pascal Van Leeuwen
2019-08-07 11:19 ` Milan Broz
2019-08-07 11:27 ` Pascal Van Leeuwen
2019-08-07 11:41 ` Milan Broz
2019-08-07 15:13 ` Pascal Van Leeuwen
2019-08-07 17:24 ` Milan Broz
2019-08-07 20:26 ` Pascal Van Leeuwen
2019-08-07 20:32 ` Ondrej Mosnáček
2019-08-07 21:13 ` Pascal Van Leeuwen
2019-08-08 4:35 ` Milan Broz [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=fcf6c4b2-b871-6fdc-7803-f94134148299@gmail.com \
--to=gmazyland@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=omosnacek@gmail.com \
--cc=pascalvanl@gmail.com \
--cc=pvanleeuwen@verimatrix.com \
--cc=rsnel@cube.dyndns.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