From: Romain Francoise <romain@orebokech.com>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au,
Chandramouli Narayanan <mouli@linux.intel.com>,
Mathias Krause <minipli@googlemail.com>
Subject: Re: v3.17-rc5: alg: skcipher: Test 4 failed on encryption for ctr-aes-aesni
Date: Tue, 16 Sep 2014 22:01:07 +0200 [thread overview]
Message-ID: <87fvfr2v3w.fsf@kima.orebokech.com> (raw)
In-Reply-To: <87sijti8kh.fsf@kima.orebokech.com> (Romain Francoise's message of "Mon, 15 Sep 2014 10:36:46 +0200")
On Mon, Sep 15, 2014 at 10:36:46AM +0200, Romain Francoise wrote:
> I upgraded from v3.16 to v3.17-rc5 and the ctr-aes-aesni encryption test
> fails, which makes my IPsec tunnels unhappy (see trace below). Before I
> start bisecting (2cddcc7df8fd3 is probably my first guess), is this
> already known?
> Sep 15 08:07:56 silenus kernel: [ 35.137145] alg: skcipher: Test 4 failed on encryption for ctr-aes-aesni [...]
Update: reverting 2cddcc7df8 ("crypto: aes - AES CTR x86_64 "by8" AVX
optimization") fixes this. This machine is Sandy Bridge (Core i7-2600),
and the problem doesn't seem to occur with the exact same kernel image
on Ivy Bridge (Xeon E3-1240v2).
next prev parent reply other threads:[~2014-09-16 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 8:36 v3.17-rc5: alg: skcipher: Test 4 failed on encryption for ctr-aes-aesni Romain Francoise
2014-09-16 20:01 ` Romain Francoise [this message]
2014-09-17 11:29 ` Herbert Xu
2014-09-21 22:28 ` Mathias Krause
2014-09-24 22:23 ` chandramouli narayanan
2014-09-25 6:27 ` Mathias Krause
2014-09-23 20:31 ` [PATCH] crypto: aesni - disable "by8" AVX CTR optimization Mathias Krause
2014-12-11 8:52 ` James Yonan
2014-12-14 17:41 ` Mathias Krause
2014-12-15 19:26 ` James Yonan
2014-12-16 21:49 ` James Yonan
2014-12-30 21:29 ` Mathias Krause
2014-09-17 20:10 ` v3.17-rc5: alg: skcipher: Test 4 failed on encryption for ctr-aes-aesni Mathias Krause
2014-09-17 20:17 ` Mathias Krause
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=87fvfr2v3w.fsf@kima.orebokech.com \
--to=romain@orebokech.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=mouli@linux.intel.com \
/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.