aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/crypto/allwinner/sun8i-ce
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2020-07-07 09:31:54 +0300
committerHerbert Xu <herbert@gondor.apana.org.au>2020-07-16 21:49:02 +1000
commit89fb00f245681d0c951cd889d3d165cf9959d70c (patch)
tree9e8710693aef5845b52cf19f6d5734674ae7b423 /drivers/crypto/allwinner/sun8i-ce
parentcrypto: omap-aes - permit asynchronous skcipher as fallback (diff)
downloadlinux-dev-89fb00f245681d0c951cd889d3d165cf9959d70c.tar.xz
linux-dev-89fb00f245681d0c951cd889d3d165cf9959d70c.zip
crypto: sun4i - permit asynchronous skcipher as fallback
Even though the sun4i driver implements asynchronous versions of ecb(aes) and cbc(aes), the fallbacks it allocates are required to be synchronous. Given that SIMD based software implementations are usually asynchronous as well, even though they rarely complete asynchronously (this typically only happens in cases where the request was made from softirq context, while SIMD was already in use in the task context that it interrupted), these implementations are disregarded, and either the generic C version or another table based version implemented in assembler is selected instead. Since falling back to synchronous AES is not only a performance issue, but potentially a security issue as well (due to the fact that table based AES is not time invariant), let's fix this, by allocating an ordinary skcipher as the fallback, and invoke it with the completion routine that was given to the outer request. Signed-off-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Corentin Labbe <clabbe.montjoie@gmail.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/allwinner/sun8i-ce')
0 files changed, 0 insertions, 0 deletions