From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Cc: Frank <frank@debian-nas.org>,
uri@jdland.co.il, linux-crypto@vger.kernel.org
Subject: Re: mv_cesa hash functions
Date: Thu, 23 Feb 2012 15:17:15 +0100 [thread overview]
Message-ID: <20120223141715.GA3506@breakpoint.cc> (raw)
In-Reply-To: <4F454BC6.7000409@gnutls.org>
On Wed, Feb 22, 2012 at 09:10:46PM +0100, Nikos Mavrogiannopoulos wrote:
> On 02/22/2012 02:03 PM, Frank wrote:
>
> > Hi,
> >
> > After doing some trials with hardware crypto offloading through usermode interfaces (af_alg and cryptodev) to Marvell CESA accelerated ciphers and hash functions with the 3.2.4 kernel's mv_cesa in Debian Wheezy on a Marvell Kirkwood system, I've noticed the following kernel output when I load the mv_cesa kernel module:
> >
> > [490889.448060] alg: hash: Test 1 failed for mv-sha1
> > [490889.452786] 00000000: c1 94 3f 2e a2 41 ce 88 d5 47 07 43 c4 a8 17 5d
> > [490889.459368] 00000010: 77 e8 47 ca
> > [490889.464321] alg: hash: Test 1 failed for mv-hmac-sha1
> > [490889.469493] 00000000: 06 71 4d 7c cc cc b5 cf 1b d6 c7 ab d0 25 c4 21
> > [490889.476068] 00000010: 66 0b 8e 70
> > Using SHA1 in a ssl/tls handshake fails in tests with mv_cesa loaded, which might be related to this.
>
>
> It might be related. I noticed the same issue in userspace with
> /dev/crypto. It can be solved by adding a 50 ms delay after the
> encryption, decryption and hashing operations. (a delay less than that
> didn't work).
It might a missing cache flush before/after the opration or before passing
the data to userland. I've seen that some hash operation fail which are not
perfromed in one go but via the start, update, end path. However I had no
time to get to the bottom of this.
>
> regards,
> Nikos
Sebastian
next prev parent reply other threads:[~2012-02-23 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 13:03 mv_cesa hash functions Frank
2012-02-22 20:10 ` Nikos Mavrogiannopoulos
2012-02-23 14:17 ` Sebastian Andrzej Siewior [this message]
2012-02-23 18:34 ` Phil Sutter
2012-02-23 18:34 ` Phil Sutter
2012-02-25 7:38 ` Herbert Xu
2012-02-27 11:17 ` [PATCH] crypto: mv_cesa - fix final callback not ignoring input data Phil Sutter
2012-02-28 8:30 ` Herbert Xu
2012-05-05 22:49 ` mv_cesa dcache problem since 2.6.37 was: Re: mv_cesa hash functions Simon Baatz
2012-05-05 22:49 ` Simon Baatz
2012-05-06 12:25 ` Russell King - ARM Linux
2012-05-06 12:25 ` Russell King - ARM Linux
2012-05-07 16:50 ` Phil Sutter
2012-05-07 16:50 ` Phil Sutter
2012-05-08 20:50 ` Simon Baatz
2012-05-08 20:50 ` Simon Baatz
2012-05-07 13:01 ` Frank
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=20120223141715.GA3506@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=frank@debian-nas.org \
--cc=linux-crypto@vger.kernel.org \
--cc=nmav@gnutls.org \
--cc=uri@jdland.co.il \
/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.