From: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
To: linux-crypto@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH 1/2] crypto: xts: fix nblocks not being updated in walk loop
Date: Sun, 23 Oct 2011 18:23:08 +0300 [thread overview]
Message-ID: <20111023152308.31041.54696.stgit@localhost6.localdomain6> (raw)
In-Reply-To: <20111023152302.31041.36522.stgit@localhost6.localdomain6>
In xts_crypt() function, nblocks should be updated after blkcipher_walk_done
call.
Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
---
crypto/xts.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/crypto/xts.c b/crypto/xts.c
index 5681d66..ca1608f 100644
--- a/crypto/xts.c
+++ b/crypto/xts.c
@@ -229,6 +229,7 @@ first:
if (!nbytes)
break;
+ nblocks = min(nbytes / bsize, max_blks);
src = (be128 *)walk.src.virt.addr;
dst = (be128 *)walk.dst.virt.addr;
}
next prev parent reply other threads:[~2011-10-23 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 15:23 [PATCH 0/2] Fixes for parallel XTS/LRW patch series Jussi Kivilinna
2011-10-23 15:23 ` Jussi Kivilinna [this message]
2011-10-23 15:23 ` [PATCH 2/2] crypto: lrw: fix nblocks not being updated in walk loop Jussi Kivilinna
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=20111023152308.31041.54696.stgit@localhost6.localdomain6 \
--to=jussi.kivilinna@mbnet.fi \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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.