On Thu, Apr 28, 2016 at 10:27:43AM +0200, Steffen Klassert wrote:
>
> The problem was that if offset (in a superpage) equals
> PAGE_SIZE in hash_walk_next(), nbytes becomes zero. So
> we map the page, but we don't hash and unmap because we
> exit the loop in shash_ahash_update() in this case.

I see.  Does this patch help?

---8<---
The length clamping in the crypto hash walk code is broken if
supplied with an offset greater than or equal to PAGE_SIZE.  This
patch fixes it by borrowing the code from scatterwalk.

Cc: <sta...@vger.kernel.org>
Reported-by: Steffen Klassert <steffen.klass...@secunet.com>
Signed-off-by: Herbert Xu <herb...@gondor.apana.org.au>

diff --git a/crypto/ahash.c b/crypto/ahash.c
index 5fc1f17..2d6c4f1 100644
--- a/crypto/ahash.c
+++ b/crypto/ahash.c
@@ -44,8 +44,8 @@ static int hash_walk_next(struct crypto_hash_walk *walk)
 {
        unsigned int alignmask = walk->alignmask;
        unsigned int offset = walk->offset;
-       unsigned int nbytes = min(walk->entrylen,
-                                 ((unsigned int)(PAGE_SIZE)) - offset);
+       unsigned int nbytes = min_t(unsigned int, walk->entrylen,
+                                   offset_in_page(~offset) + 1);
 
        if (walk->flags & CRYPTO_ALG_ASYNC)
                walk->data = kmap(walk->pg);
@@ -91,8 +91,8 @@ int crypto_hash_walk_done(struct crypto_hash_walk *walk, int 
err)
                walk->offset = ALIGN(walk->offset, alignmask + 1);
                walk->data += walk->offset;
 
-               nbytes = min(nbytes,
-                            ((unsigned int)(PAGE_SIZE)) - walk->offset);
+               nbytes = min_t(unsigned int, nbytes,
+                              offset_in_page(~walk->offset) + 1);
                walk->entrylen -= nbytes;
 
                return nbytes;
-- 
Email: Herbert Xu <herb...@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to