From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v4 0/4] crypto: lrw - Fixes and improvements
Date: Fri, 21 Sep 2018 13:45:34 +0800 [thread overview]
Message-ID: <20180921054534.7iqfb3omlowromhr@gondor.apana.org.au> (raw)
In-Reply-To: <20180913085134.11694-1-omosnace@redhat.com>
On Thu, Sep 13, 2018 at 10:51:30AM +0200, Ondrej Mosnacek wrote:
> This patchset contains a corner-case fix and several improvements for
> the LRW template.
>
> The first patch fixes an out-of-bounds array access (and subsequently
> incorrect cipher output) when the LRW counter goes from all ones to all
> zeros. This patch should be applied to the crypto-2.6 tree and also go
> to stable.
>
> The second patch adds a test vector for lrw(aes) that covers the above
> bug.
>
> The third patch is a small optimization of the LRW tweak computation.
>
> The fourth patch is a follow-up to a similar patch for XTS (it
> simplifies away the use of dynamically allocated auxiliary buffer to
> cache the computed tweak values):
> https://patchwork.kernel.org/patch/10588775/
>
> Patches 2-4 should be applied only to cryptodev-2.6, but they all depend
> on the first patch.
>
> Changes in v4:
> - applied various corrections/suggestions from Eric Biggers
> - added a fix for buggy behavior on counter wrap-around (+ test vector)
>
> v3: https://www.spinics.net/lists/linux-crypto/msg34946.html
> Changes in v3:
> - fix a copy-paste error
>
> v2: https://www.spinics.net/lists/linux-crypto/msg34890.html
> Changes in v2:
> - small cleanup suggested by Eric Biggers
>
> v1: https://www.spinics.net/lists/linux-crypto/msg34871.html
>
> Ondrej Mosnacek (4):
> crypto: lrw - Fix out-of bounds access on counter overflow
> crypto: testmgr - Add test for LRW counter wrap-around
> crypto: lrw - Optimize tweak computation
> crypto: lrw - Do not use auxiliary buffer
>
> crypto/lrw.c | 342 +++++++++++++----------------------------------
> crypto/testmgr.h | 21 +++
> 2 files changed, 112 insertions(+), 251 deletions(-)
All applied. 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:[~2018-09-21 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 8:51 [PATCH v4 0/4] crypto: lrw - Fixes and improvements Ondrej Mosnacek
2018-09-13 8:51 ` [PATCH v4 1/4] crypto: lrw - Fix out-of bounds access on counter overflow Ondrej Mosnacek
2018-09-13 8:51 ` [PATCH v4 2/4] crypto: testmgr - Add test for LRW counter wrap-around Ondrej Mosnacek
2018-09-13 8:51 ` [PATCH v4 3/4] crypto: lrw - Optimize tweak computation Ondrej Mosnacek
2018-09-13 8:51 ` [PATCH v4 4/4] crypto: lrw - Do not use auxiliary buffer Ondrej Mosnacek
2018-09-21 5:45 ` Herbert Xu [this message]
2018-09-30 19:00 ` [PATCH v4 0/4] crypto: lrw - Fixes and improvements Ard Biesheuvel
2018-09-30 19:40 ` Ard Biesheuvel
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=20180921054534.7iqfb3omlowromhr@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dm-devel@redhat.com \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=omosnace@redhat.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;
as well as URLs for NNTP newsgroup(s).