From: Ard Biesheuvel <ardb@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, Ard Biesheuvel <ardb@kernel.org>,
Ondrej Mosnacek <omosnacek@gmail.com>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH v2 0/4] crypto: aegis128 enhancements
Date: Tue, 10 Nov 2020 20:04:40 +0100 [thread overview]
Message-ID: <20201110190444.10634-1-ardb@kernel.org> (raw)
This series supersedes [0] '[PATCH] crypto: aegis128/neon - optimize tail
block handling', which is included as patch #3 here, but hasn't been
modified substantially.
Patch #1 should probably go to -stable, even though aegis128 does not appear
to be widely used.
Patches #2 and #3 improve the SIMD code paths.
Patch #4 enables fuzz testing for the SIMD code by registering the generic
code as a separate driver if the SIMD code path is enabled.
Cc: Ondrej Mosnacek <omosnacek@gmail.com>
Cc: Eric Biggers <ebiggers@kernel.org>
[0] https://lore.kernel.org/linux-crypto/20201107195516.13952-1-ardb@kernel.org/
Ard Biesheuvel (4):
crypto: aegis128 - wipe plaintext and tag if decryption fails
crypto: aegis128/neon - optimize tail block handling
crypto: aegis128/neon - move final tag check to SIMD domain
crypto: aegis128 - expose SIMD code path as separate driver
crypto/aegis128-core.c | 201 ++++++++++++++------
crypto/aegis128-neon-inner.c | 122 ++++++++++--
crypto/aegis128-neon.c | 21 +-
3 files changed, 263 insertions(+), 81 deletions(-)
--
2.17.1
next reply other threads:[~2020-11-10 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 19:04 Ard Biesheuvel [this message]
2020-11-10 19:04 ` [PATCH v2 1/4] crypto: aegis128 - wipe plaintext and tag if decryption fails Ard Biesheuvel
2020-11-11 17:36 ` Ondrej Mosnáček
2020-11-10 19:04 ` [PATCH v2 2/4] crypto: aegis128/neon - optimize tail block handling Ard Biesheuvel
2020-11-10 19:04 ` [PATCH v2 3/4] crypto: aegis128/neon - move final tag check to SIMD domain Ard Biesheuvel
2020-11-10 19:04 ` [PATCH v2 4/4] crypto: aegis128 - expose SIMD code path as separate driver Ard Biesheuvel
2020-11-11 17:46 ` Ondrej Mosnáček
2020-11-12 8:18 ` 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=20201110190444.10634-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=omosnacek@gmail.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 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.