From: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
Fionnuala Gunter <fin@linux.vnet.ibm.com>,
Joel Schopp <jschopp@linux.vnet.ibm.com>,
Joy Latten <jmlatten@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] drivers/crypto/nx: fix limits to sg lists for SHA-2
Date: Mon, 29 Jul 2013 12:19:12 -0300 [thread overview]
Message-ID: <20130729151912.GA4947@oc8526070481.ibm.com> (raw)
In-Reply-To: <1374877892.9200.30.camel@pasglop>
We think that it's very likely that AES may also be affected by a
similar problem. But we still have to test it and I'd like to provide a
separated patch for it.
Regards,
Marcelo
On Sat, Jul 27, 2013 at 08:31:32AM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2013-07-26 at 14:08 -0300, Marcelo Cerri wrote:
> > ---
> > drivers/crypto/nx/nx-sha256.c | 108 +++++++++++++++++++++++-----------------
> > drivers/crypto/nx/nx-sha512.c | 113 ++++++++++++++++++++++++------------------
> > 2 files changed, 129 insertions(+), 92 deletions(-)
>
> What about the other nx drivers ? They are not affected ?
>
> Cheers,
> Ben.
>
>
next prev parent reply other threads:[~2013-07-29 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 17:08 [PATCH 0/2] drivers/crypto/nx: fixes when input data is too large Marcelo Cerri
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 [this message]
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=20130729151912.GA4947@oc8526070481.ibm.com \
--to=mhcerri@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=fin@linux.vnet.ibm.com \
--cc=jmlatten@linux.vnet.ibm.com \
--cc=jschopp@linux.vnet.ibm.com \
--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
all inboxes | Powered by JetHome®