linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
Subject: [PATCH 0/2] drivers/crypto/nx: fixes when input data is too large
Date: Fri, 26 Jul 2013 14:08:06 -0300	[thread overview]
Message-ID: <1374858488-24658-1-git-send-email-mhcerri@linux.vnet.ibm.com> (raw)

This series of patches fixes two bugs that are triggered when the input data is
too large. The first one is caused by the miscalculation of physical addresses
and the second one by some limits that the co-processor has to the input data.

Marcelo Cerri (2):
  drivers/crypto/nx: fix physical addresses added to sg lists
  drivers/crypto/nx: fix limits to sg lists for SHA-2

 drivers/crypto/nx/nx-sha256.c | 108 +++++++++++++++++++++++-----------------
 drivers/crypto/nx/nx-sha512.c | 113 ++++++++++++++++++++++++------------------
 drivers/crypto/nx/nx.c        |  22 ++++++--
 3 files changed, 148 insertions(+), 95 deletions(-)

-- 
1.7.12


             reply	other threads:[~2013-07-26 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 17:08 Marcelo Cerri [this message]
2013-07-26 17:08 ` [PATCH 1/2] drivers/crypto/nx: fix physical addresses added to sg lists Marcelo Cerri
2013-07-26 17:08 ` [PATCH 2/2] drivers/crypto/nx: fix limits to sg lists for SHA-2 Marcelo Cerri
2013-07-26 22:29   ` Benjamin Herrenschmidt
2013-07-29 15:24     ` Marcelo Cerri
2013-07-26 22:31   ` Benjamin Herrenschmidt
2013-07-29 15:19     ` Marcelo Cerri
2013-08-01  9:26 ` [PATCH 0/2] drivers/crypto/nx: fixes when input data is too large Benjamin Herrenschmidt

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=1374858488-24658-1-git-send-email-mhcerri@linux.vnet.ibm.com \
    --to=mhcerri@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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 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).