From: Mandeep Singh Baines <msb@chromium.org>
To: David Miller <davem@davemloft.net>
Cc: msb@chromium.org, linux-kernel@vger.kernel.org,
herbert@gondor.hengli.com.au, linux-crypto@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: [PATCH v2] crypto: sha1: modify sha1_update to use SHA1_BLOCK_SIZE
Date: Thu, 26 May 2011 16:20:58 -0700 [thread overview]
Message-ID: <20110526232058.GQ11023@google.com> (raw)
In-Reply-To: <20110525.233411.1372538972166578285.davem@davemloft.net>
David Miller (davem@davemloft.net) wrote:
>
> The temp[] buffer is explicitly places inside the inner most
> basic block so that the compiler doesn't allocate the stack
> space unless that code path is taken.
>
Fixed in V2 (this patch). Thanks for the review.
-- >8 -- (snip)
Plus some other minor cleanup.
Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David S. Miller <davem@davemloft.net>
Cc: Joe Perches <joe@perches.com>
Cc: linux-crypto@vger.kernel.org
---
crypto/sha1_generic.c | 33 +++++++++++++++------------------
1 files changed, 15 insertions(+), 18 deletions(-)
diff --git a/crypto/sha1_generic.c b/crypto/sha1_generic.c
index 0416091..0b56719 100644
--- a/crypto/sha1_generic.c
+++ b/crypto/sha1_generic.c
@@ -40,33 +40,30 @@ static int sha1_update(struct shash_desc *desc, const u8 *data,
unsigned int len)
{
struct sha1_state *sctx = shash_desc_ctx(desc);
- unsigned int partial, done;
- const u8 *src;
+ unsigned int partial = sctx->count % SHA1_BLOCK_SIZE;
- partial = sctx->count & 0x3f;
sctx->count += len;
- done = 0;
- src = data;
- if ((partial + len) > 63) {
+ if ((partial + len) >= SHA1_BLOCK_SIZE) {
u32 temp[SHA_WORKSPACE_WORDS];
if (partial) {
- done = -partial;
- memcpy(sctx->buffer + partial, data, done + 64);
- src = sctx->buffer;
- }
-
- do {
- sha_transform(sctx->state, src, temp);
- done += 64;
- src = data + done;
- } while (done + 63 < len);
+ unsigned int done = SHA1_BLOCK_SIZE - partial;
+ memcpy(sctx->buffer + partial, data, done);
+ sha_transform(sctx->state, sctx->buffer, temp);
+ len -= done;
+ data += done;
+ partial = 0;
+ }
+ while (len >= SHA1_BLOCK_SIZE) {
+ sha_transform(sctx->state, data, temp);
+ len -= SHA1_BLOCK_SIZE;
+ data += SHA1_BLOCK_SIZE;
+ }
memset(temp, 0, sizeof(temp));
- partial = 0;
}
- memcpy(sctx->buffer + partial, src, len - done);
+ memcpy(sctx->buffer + partial, data, len);
return 0;
}
--
1.7.3.1
next prev parent reply other threads:[~2011-05-26 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 3:11 [PATCH] crypto: sha1: modify sha1_update to use SHA1_BLOCK_SIZE Mandeep Singh Baines
2011-05-26 3:34 ` David Miller
2011-05-26 3:52 ` Joe Perches
2011-05-26 23:20 ` Mandeep Singh Baines [this message]
2011-05-31 5:22 ` [PATCH v2] " Herbert Xu
2011-06-23 19:02 ` [PATCH v3] crypto: sha1: " Mandeep Singh Baines
2011-06-27 7: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=20110526232058.GQ11023@google.com \
--to=msb@chromium.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=joe@perches.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox