From: Mathias Krause <minipli@googlemail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Romain Francoise <romain@orebokech.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Linux 3.6-rc5
Date: Sun, 9 Sep 2012 22:09:10 +0200 [thread overview]
Message-ID: <20120909200910.GA11919@r00tworld.net> (raw)
In-Reply-To: <20120909191958.GB9782@gondor.apana.org.au>
On Sun, Sep 09, 2012 at 12:19:58PM -0700, Herbert Xu wrote:
> On Sun, Sep 09, 2012 at 11:13:02AM +0200, Romain Francoise wrote:
> > Still seeing this BUG with -rc5, that I originally reported here:
> > http://marc.info/?l=linux-crypto-vger&m=134653220530264&w=2
> >
> > [ 26.362567] ------------[ cut here ]------------
> > [ 26.362583] kernel BUG at crypto/scatterwalk.c:37!
> > [ 26.362606] invalid opcode: 0000 [#1] SMP
>
> Can you try blacklisting/not loading sha1_ssse3 and aesni_intel
> to see which one of them is causing this crash? Of course if you
> can still reproduce this without loading either of them that would
> also be interesting to know.
It happens with the C variants of SHA1 and AES, too. You can easily
trigger the bug with Steffen's crconf[1]:
$ crconf add alg "authenc(hmac(sha1-generic),cbc(aes-generic))" type 3
So the problem is likely not related to sha1-ssse3.ko or aesni-intel.ko.
Regards,
Mathias
[1] http://sourceforge.net/projects/crconf/
WARNING: multiple messages have this Message-ID (diff)
From: Mathias Krause <minipli@googlemail.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Romain Francoise <romain@orebokech.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Linux 3.6-rc5
Date: Sun, 9 Sep 2012 22:09:10 +0200 [thread overview]
Message-ID: <20120909200910.GA11919@r00tworld.net> (raw)
In-Reply-To: <20120909191958.GB9782@gondor.apana.org.au>
On Sun, Sep 09, 2012 at 12:19:58PM -0700, Herbert Xu wrote:
> On Sun, Sep 09, 2012 at 11:13:02AM +0200, Romain Francoise wrote:
> > Still seeing this BUG with -rc5, that I originally reported here:
> > http://marc.info/?l=linux-crypto-vger&m=134653220530264&w=2
> >
> > [ 26.362567] ------------[ cut here ]------------
> > [ 26.362583] kernel BUG at crypto/scatterwalk.c:37!
> > [ 26.362606] invalid opcode: 0000 [#1] SMP
>
> Can you try blacklisting/not loading sha1_ssse3 and aesni_intel
> to see which one of them is causing this crash? Of course if you
> can still reproduce this without loading either of them that would
> also be interesting to know.
It happens with the C variants of SHA1 and AES, too. You can easily
trigger the bug with Steffen's crconf[1]:
$ crconf add alg "authenc(hmac(sha1-generic),cbc(aes-generic))" type 3
So the problem is likely not related to sha1-ssse3.ko or aesni-intel.ko.
Regards,
Mathias
[1] http://sourceforge.net/projects/crconf/
next prev parent reply other threads:[~2012-09-09 20:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 0:18 Linux 3.6-rc5 Linus Torvalds
2012-09-09 9:13 ` Romain Francoise
2012-09-09 9:13 ` Romain Francoise
2012-09-09 12:54 ` Jussi Kivilinna
2012-09-09 12:54 ` Jussi Kivilinna
2012-09-09 14:23 ` Romain Francoise
2012-09-09 14:23 ` Romain Francoise
2012-09-09 15:35 ` Linus Torvalds
2012-09-09 15:35 ` Linus Torvalds
2012-09-09 18:53 ` Herbert Xu
2012-09-09 18:53 ` Herbert Xu
2012-09-09 20:54 ` Jussi Kivilinna
2012-09-09 20:54 ` Jussi Kivilinna
2012-09-09 21:01 ` Herbert Xu
2012-09-09 21:01 ` Herbert Xu
2012-09-09 19:19 ` Herbert Xu
2012-09-09 19:19 ` Herbert Xu
2012-09-09 20:09 ` Mathias Krause [this message]
2012-09-09 20:09 ` Mathias Krause
2012-09-09 21:00 ` Herbert Xu
2012-09-09 21:00 ` Herbert Xu
2012-09-09 21:09 ` Mathias Krause
2012-09-09 21:09 ` Mathias Krause
2012-09-10 17:18 ` Romain Francoise
2012-09-10 17:18 ` Romain Francoise
2012-09-09 20:26 ` Jussi Kivilinna
2012-09-09 20:26 ` Jussi Kivilinna
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=20120909200910.GA11919@r00tworld.net \
--to=minipli@googlemail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romain@orebokech.com \
--cc=torvalds@linux-foundation.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.