All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: sha384 self-test failure oddity
Date: Tue, 16 Jun 2009 08:39:42 -0400	[thread overview]
Message-ID: <200906160839.42886.jarod@redhat.com> (raw)
In-Reply-To: <20090616112250.GA13218@gondor.apana.org.au>

On Tuesday 16 June 2009 07:22:50 Herbert Xu wrote:
> On Tue, Jun 02, 2009 at 03:41:34PM -0400, Jarod Wilson wrote:
> > On Tuesday 02 June 2009 09:20:38 Herbert Xu wrote:
> > > On Tue, Jun 02, 2009 at 09:01:42AM -0400, Jarod Wilson wrote:
> > > >
> > > > > I can't reproduce this with 2.6.30-rc7.
> > > > 
> > > > I'll rebase my cryptodev tree to 2.6.30-rcX and see if I can still
> > > > reproduce the problem.
> > > 
> > > I just rebased cryptodev against 2.6.30-rc7 today so please let
> > > me know whether you can still reproduce it with cryptodev.
> > 
> > Still happens after the rebase. Kernel config here, if it helps:
> > 
> > http://jwilson.fedorapeople.org/misc/cryptodev-2.6-config
> 
> Sorry, I still have no luck in reproducing this.  I used the current
> linux-2.6 which has the cryptodev tree merged, and the crypto bits from
> your config file.
> 
> Any chance you can let me log onto your system to have a look?

Sure, I'll drop you the access info off-list in a sec.

-- 
Jarod Wilson
jarod@redhat.com

      reply	other threads:[~2009-06-16 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 18:35 sha384 self-test failure oddity Jarod Wilson
2009-06-02  5:10 ` Herbert Xu
2009-06-02 13:01   ` Jarod Wilson
2009-06-02 13:20     ` Herbert Xu
2009-06-02 19:41       ` Jarod Wilson
2009-06-16 11:22         ` Herbert Xu
2009-06-16 12:39           ` Jarod Wilson [this message]

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=200906160839.42886.jarod@redhat.com \
    --to=jarod@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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 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.