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
Hi,
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:
the fallback code-path even when we could still execute
the digest function. However, this isn't a big deal as nobody
but the test path would supply zero-length associated data.
Reported-by: Romain Francoise rom...@orebokech.com
Signed-off-by: Herbert Xu herb...@gondor.apana.org.au
Feel free
Still seeing this BUG with -rc5, that I originally reported here:
http://marc.info/?l=linux-crypto-vgerm=134653220530264w=2
[ 26.362567] [ cut here ]
[ 26.362583] kernel BUG at crypto/scatterwalk.c:37!
[ 26.362606] invalid opcode: [#1] SMP
[ 26.362622]
Jussi Kivilinna jussi.kivili...@mbnet.fi writes:
Does reverting e46e9a46386bca8e80a6467b5c643dc494861896 help?
It does, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at
I get the following BUG when setting up an IPsec SA. The aead combination
under test when that happens is authenc(hmac(sha1-ssse3),cbc-aes-aesni),
it remains in 'selftest: unknown' status in /proc/crypto.
Thanks,
[ cut here ]
kernel BUG at crypto/scatterwalk.c:37!
invalid
