On Mon, 2014-11-10 at 11:50 +0100, Ondrej Kozina wrote:
> Hello,
>
> could you please add this patch (already landed in 3.18-rc1) to
> following stable kernels:
>
> 3.17.x, 3.14.x, 3.12.x, 3.4.x, 3.2.x?
>
> The bugfix allows usage of crypto API socket on archs with PAGE_SIZE >=
> 32 KiB (I hav
On Thu, 4 Dec 2014 18:22:45 -0600
Kim Phillips wrote:
> On Thu, 6 Nov 2014 23:17:14 +0800
> Herbert Xu wrote:
>
> > On Thu, Oct 30, 2014 at 06:55:07PM +0200, Tudor Ambarus wrote:
> > > Add AES-GMAC as an IPSec ESP mechanism to provide
> > > data origin authentication, but not confidentiality.
>
Steffen Trumtrar wrote:
>
> Everything works fine if I do not complete the request from the
> backlog, but instead complete the request when it is due.
> Alternative: make the queue deeper like some drivers have it.
> If the queue is deeper than I have threads, it works, because
> the requests nev
Hi Linus:
Here is the crypto update for 3.19:
* The crypto API is now documented :)
* Disallow arbitrary module loading through crypto API.
* Allow get request with empty driver name through crypto_user.
* Allow speed testing of arbitrary hash functions.
* Add caam support for ctr(aes), gcm(aes)
I'm seeing some anomalous results with the "by8" AVX CTR optimization in
3.18.
In particular, crypto_aead_encrypt appears to produce different
ciphertext from the same plaintext depending on whether or not the
optimization is enabled.
See the attached patch to tcrypt that demonstrates the di
