From: Tim Chen <tim.c.chen@linux.intel.com>
To: Eric Biggers <ebiggers3@gmail.com>,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Biggers <ebiggers@google.com>,
Megha Dey <megha.dey@linux.intel.com>
Subject: Re: [PATCH] crypto: sha1-mb - remove HASH_FIRST flag
Date: Thu, 25 Jan 2018 13:58:38 -0800 [thread overview]
Message-ID: <b5918f68-e4d3-e98c-00eb-d54c2d6e3329@linux.intel.com> (raw)
In-Reply-To: <20180125031008.778-1-ebiggers3@gmail.com>
On 01/24/2018 07:10 PM, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> The HASH_FIRST flag is never set. Remove it.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> arch/x86/crypto/sha1-mb/sha1_mb.c | 28 +++-------------------------
> arch/x86/crypto/sha1-mb/sha1_mb_ctx.h | 8 +++-----
> 2 files changed, 6 insertions(+), 30 deletions(-)
>
> diff --git a/arch/x86/crypto/sha1-mb/sha1_mb.c b/arch/x86/crypto/sha1-mb/sha1_mb.c
> index acf9fdf01671..e17655ffde79 100644
> --- a/arch/x86/crypto/sha1-mb/sha1_mb.c
> +++ b/arch/x86/crypto/sha1-mb/sha1_mb.c
> @@ -106,13 +106,6 @@ static asmlinkage struct job_sha1* (*sha1_job_mgr_flush)
> static asmlinkage struct job_sha1* (*sha1_job_mgr_get_comp_job)
> (struct sha1_mb_mgr *state);
>
> -static inline void sha1_init_digest(uint32_t *digest)
> -{
> - static const uint32_t initial_digest[SHA1_DIGEST_LENGTH] = {SHA1_H0,
> - SHA1_H1, SHA1_H2, SHA1_H3, SHA1_H4 };
> - memcpy(digest, initial_digest, sizeof(initial_digest));
> -}
> -
> static inline uint32_t sha1_pad(uint8_t padblock[SHA1_BLOCK_SIZE * 2],
> uint64_t total_len)
> {
> @@ -244,11 +237,8 @@ static struct sha1_hash_ctx *sha1_ctx_mgr_submit(struct sha1_ctx_mgr *mgr,
> uint32_t len,
> int flags)
> {
> - if (flags & (~HASH_ENTIRE)) {
> - /*
> - * User should not pass anything other than FIRST, UPDATE, or
> - * LAST
> - */
> + if (flags & ~(HASH_UPDATE | HASH_LAST)) {
> + /* User should not pass anything other than UPDATE or LAST */
> ctx->error = HASH_CTX_ERROR_INVALID_FLAGS;
> return ctx;
> }
> @@ -259,24 +249,12 @@ static struct sha1_hash_ctx *sha1_ctx_mgr_submit(struct sha1_ctx_mgr *mgr,
> return ctx;
> }
>
> - if ((ctx->status & HASH_CTX_STS_COMPLETE) && !(flags & HASH_FIRST)) {
> + if (ctx->status & HASH_CTX_STS_COMPLETE) {
> /* Cannot update a finished job. */
> ctx->error = HASH_CTX_ERROR_ALREADY_COMPLETED;
> return ctx;
> }
>
> -
> - if (flags & HASH_FIRST) {
> - /* Init digest */
> - sha1_init_digest(ctx->job.result_digest);
> -
> - /* Reset byte counter */
> - ctx->total_length = 0;
> -
> - /* Clear extra blocks */
> - ctx->partial_block_buffer_length = 0;
> - }
> -
I suppose this will be okay as we are really doing the initialization in
sha1_mb_init. Megha is now maintaining this code. Copying her
so she can do some verification of this change.
Tim
> /*
> * If we made it here, there were no errors during this call to
> * submit
> diff --git a/arch/x86/crypto/sha1-mb/sha1_mb_ctx.h b/arch/x86/crypto/sha1-mb/sha1_mb_ctx.h
> index 13590ccf965c..9454bd16f9f8 100644
> --- a/arch/x86/crypto/sha1-mb/sha1_mb_ctx.h
> +++ b/arch/x86/crypto/sha1-mb/sha1_mb_ctx.h
> @@ -57,11 +57,9 @@
> #include "sha1_mb_mgr.h"
>
> #define HASH_UPDATE 0x00
> -#define HASH_FIRST 0x01
> -#define HASH_LAST 0x02
> -#define HASH_ENTIRE 0x03
> -#define HASH_DONE 0x04
> -#define HASH_FINAL 0x08
> +#define HASH_LAST 0x01
> +#define HASH_DONE 0x02
> +#define HASH_FINAL 0x04
>
> #define HASH_CTX_STS_IDLE 0x00
> #define HASH_CTX_STS_PROCESSING 0x01
>
next prev parent reply other threads:[~2018-01-25 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 3:10 [PATCH] crypto: sha1-mb - remove HASH_FIRST flag Eric Biggers
2018-01-25 21:58 ` Tim Chen [this message]
2018-01-25 22:03 ` Eric Biggers
2018-01-30 1:09 ` Tim Chen
2018-02-15 15:42 ` Herbert Xu
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=b5918f68-e4d3-e98c-00eb-d54c2d6e3329@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=megha.dey@linux.intel.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).