From: David Sterba <dsterba@suse.cz>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: David Sterba <dsterba@suse.com>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH v6 0/2] BLAKE2b generic implementation
Date: Wed, 23 Oct 2019 20:11:20 +0200 [thread overview]
Message-ID: <20191023181120.GF3001@suse.cz> (raw)
In-Reply-To: <CAKv+Gu_yhm2hL+Sx6ZC3xWLcWuJLn+0erQaK6_NpL-aZo72AbA@mail.gmail.com>
On Wed, Oct 23, 2019 at 11:01:25AM +0200, Ard Biesheuvel wrote:
> On Wed, 23 Oct 2019 at 02:12, David Sterba <dsterba@suse.com> wrote:
> > Tested on x86_64 with KASAN and SLUB_DEBUG.
>
> Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> # arm64 big-endian
Thanks!
> > crypto/Kconfig | 17 ++
> > crypto/Makefile | 1 +
> > crypto/blake2b_generic.c | 413 +++++++++++++++++++++++++++++++++++++++
> > crypto/testmgr.c | 28 +++
> > crypto/testmgr.h | 307 +++++++++++++++++++++++++++++
> > include/crypto/blake2b.h | 46 +++++
>
> Final nit: do we need this header file at all? Could we move the
> contents into crypto/blake2b_generic.c? Or is the btrfs code going to
> #include it?
The only interesting part for btrfs would be the definition of
BLAKE2B_256_DIGEST_SIZE instead of hardcoding the number. As the patches
go through separate trees I have to use the hardcoded number anyway.
The header would make sense for the library version of blake2b, similar
to what the wireguard blake2s patches do, but there's no need for that
right now so I guess the header can be folded to .c.
prev parent reply other threads:[~2019-10-23 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 0:12 [PATCH v6 0/2] BLAKE2b generic implementation David Sterba
2019-10-23 0:12 ` [PATCH v6 1/2] crypto: add blake2b " David Sterba
2019-10-23 0:12 ` [PATCH v6 2/2] crypto: add test vectors for blake2b David Sterba
2019-10-23 9:01 ` [PATCH v6 0/2] BLAKE2b generic implementation Ard Biesheuvel
2019-10-23 18:11 ` David Sterba [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=20191023181120.GF3001@suse.cz \
--to=dsterba@suse.cz \
--cc=ard.biesheuvel@linaro.org \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--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 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.