On Mon, Jun 01, 2015 at 11:04:39AM +0200, Stephan Mueller wrote: > > Just FYI: when testing rfc4106(gcm(aes-aesni)) with the old givcipher API, I > got a crash in my code invoking the cipher which used to work in older kernels > and which works with the C implementations. So, there must be some change in > how givcipher is treated by the AESNI implementation. > > As this API is sunset now, shall I dig deeper or shall we simply deactivate > the API entirely? What do you mean by the old givcipher API? Are you referring to the old algif_aead that was disabled? Can you show me the crash that you got and as much information as you can about the caller that triggered the crash? The assumption at this point is that all users outside of crypto/ itself are gone. But I'd still like to look at the crash just in case it's relevant for users within crypto. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
