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 0/2] Fixes for parallel XTS/LRW patch series
Date: Sun, 23 Oct 2011 18:23:02 +0300 [thread overview]
Message-ID: <20111023152302.31041.36522.stgit@localhost6.localdomain6> (raw)
These patches fix bug in xts_crypt()/lrw_crypt() where nblocks is
not updated in the block walk loop.
This causes nblocks to be left at 0, after blkcipher_walk_done() call.
This leads 'do { ... } while (nblocks > 0)' loop to be run one extra
time with nblocks == 0 and at end of do-while loop nblocks gets updated
correctly.
---
Jussi Kivilinna (2):
crypto: xts: fix nblocks not being updated in walk loop
crypto: lrw: fix nblocks not being updated in walk loop
crypto/lrw.c | 1 +
crypto/xts.c | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
next 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 Jussi Kivilinna [this message]
2011-10-23 15:23 ` [PATCH 1/2] crypto: xts: fix nblocks not being updated in walk loop Jussi Kivilinna
2011-10-23 15:23 ` [PATCH 2/2] crypto: lrw: " 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=20111023152302.31041.36522.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.