On Tue, Nov 19, 2013 at 11:22:12AM +0100, Harald Freudenberger wrote: > The aes-ctr mode used one preallocated page without any concurrency > protection. When multiple threads run aes-ctr encryption or decryption > this could lead to data corruption. > > The patch introduces locking for the preallocated page and alternatively > allocating and freeing of an temp page in concurrency situations. You can't use mutex_lock because you may be in a non-sleepable context. Perhaps just fall back to doing it block-by-block, like we do in aesni-intel on x86? I have to say that your hardware has a funny way of doing CTR. Somebody was generalising out of their backside :) 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
