From: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
To: herbert@gondor.apana.org.au
Cc: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: [PATCH v2 00/10] Series of fixes for NX driver
Date: Thu, 29 Aug 2013 11:36:30 -0300 [thread overview]
Message-ID: <1377787000-4966-1-git-send-email-mhcerri@linux.vnet.ibm.com> (raw)
This series of patches contains fixes in several algorithms implemented
by the NX driver. The patches can be separated in three different
categories:
- Changes to split the data in several hyper calls to respect the
limits of data that the co-processador can handle. This affects
all AES modes.
- Fixes in how the driver handle zero length messages. This affects
XCBC and GCM.
- Fixes for SHA-2 when chunks bigger than the block size are provided.
v2:
- Fixed conflict.
Fionnuala Gunter (2):
crypto: nx - fix limits to sg lists for AES-XCBC
crypto: nx - fix limits to sg lists for AES-CCM
Marcelo Cerri (8):
crypto: nx - add offset to nx_build_sg_lists()
crypto: nx - fix limits to sg lists for AES-ECB
crypto: nx - fix limits to sg lists for AES-CBC
crypto: nx - fix limits to sg lists for AES-CTR
crypto: nx - fix limits to sg lists for AES-GCM
crypto: nx - fix XCBC for zero length messages
crypto: nx - fix GCM for zero length messages
crypto: nx - fix SHA-2 for chunks bigger than block size
drivers/crypto/nx/nx-aes-cbc.c | 50 ++++---
drivers/crypto/nx/nx-aes-ccm.c | 297 +++++++++++++++++++++++++++++-----------
drivers/crypto/nx/nx-aes-ctr.c | 50 ++++---
drivers/crypto/nx/nx-aes-ecb.c | 48 ++++---
drivers/crypto/nx/nx-aes-gcm.c | 292 ++++++++++++++++++++++++++++++---------
drivers/crypto/nx/nx-aes-xcbc.c | 191 +++++++++++++++++++-------
drivers/crypto/nx/nx-sha256.c | 2 +-
drivers/crypto/nx/nx-sha512.c | 2 +-
drivers/crypto/nx/nx.c | 9 +-
drivers/crypto/nx/nx.h | 2 +-
10 files changed, 683 insertions(+), 260 deletions(-)
--
1.7.12
next reply other threads:[~2013-08-29 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 14:36 Marcelo Cerri [this message]
2013-08-29 14:36 ` [PATCH v2 01/10] crypto: nx - add offset to nx_build_sg_lists() Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 02/10] crypto: nx - fix limits to sg lists for AES-ECB Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 03/10] crypto: nx - fix limits to sg lists for AES-CBC Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 04/10] crypto: nx - fix limits to sg lists for AES-CTR Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 05/10] crypto: nx - fix limits to sg lists for AES-GCM Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 06/10] crypto: nx - fix limits to sg lists for AES-XCBC Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 07/10] crypto: nx - fix limits to sg lists for AES-CCM Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 08/10] crypto: nx - fix XCBC for zero length messages Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 09/10] crypto: nx - fix GCM " Marcelo Cerri
2013-08-29 14:36 ` [PATCH v2 10/10] crypto: nx - fix SHA-2 for chunks bigger than block size Marcelo Cerri
2013-09-02 10:35 ` [PATCH v2 00/10] Series of fixes for NX driver 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=1377787000-4966-1-git-send-email-mhcerri@linux.vnet.ibm.com \
--to=mhcerri@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).