From: "Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>
To: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org,
Marcelo Henrique Cerri <mhcerri@linux.vnet.ibm.com>,
Fionnuala Gunter <fin@linux.vnet.ibm.com>
Subject: [PATCH 0/9] NX crypto driver fixes
Date: Tue, 28 Oct 2014 15:40:09 -0200 [thread overview]
Message-ID: <20141028174006.GA15893@bluepex.com> (raw)
This patch set fixes the follow issues in NX crypto driver:
- Bound limit issue that causes a memory crash
- SHA concurrence issue
- IV vector fix with the correct bit order
- NX CCM does not support keys larger than 128 causing
crashes in fips mode.
Leonidas S. Barbosa (9):
Moving NX-AES-CBC to be process logic
Moving NX-AES-CCM to be process logic and sg_list bounds
Moving limit and bound logic in CTR and fix IV vector
Moving NX-AES-ECB to be processed logic
Moving NX-AES-GCM to be processed logic
Moving NX-AES-XCBC to be processed logic
Fix SHA concurrence issue and sg limit bounds
Fixing the limit number of bytes to be processed
Disable ccm and ccm4309 in fips mod
drivers/crypto/nx/nx-aes-cbc.c | 12 +--
drivers/crypto/nx/nx-aes-ccm.c | 61 +++++------
drivers/crypto/nx/nx-aes-ctr.c | 13 +--
drivers/crypto/nx/nx-aes-ecb.c | 12 +--
drivers/crypto/nx/nx-aes-gcm.c | 66 +++++++-----
drivers/crypto/nx/nx-aes-xcbc.c | 81 +++++++++++---
drivers/crypto/nx/nx-sha256.c | 208 ++++++++++++++++++-------------------
drivers/crypto/nx/nx-sha512.c | 222 ++++++++++++++++++---------------------
drivers/crypto/nx/nx.c | 159 +++++++++++++++++++++++-----
drivers/crypto/nx/nx.h | 8 +-
10 files changed, 469 insertions(+), 373 deletions(-)
next reply other threads:[~2014-10-28 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:40 Leonidas S. Barbosa [this message]
2014-11-06 15:17 ` [PATCH 0/9] NX crypto driver fixes 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=20141028174006.GA15893@bluepex.com \
--to=leosilva@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=fin@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhcerri@linux.vnet.ibm.com \
/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).