fscrypt: Don't use asynchronous CryptoAPI algorithms
authorEric Biggers <ebiggers@kernel.org>
Thu, 10 Jul 2025 06:07:48 +0000 (23:07 -0700)
committerEric Biggers <ebiggers@kernel.org>
Thu, 10 Jul 2025 19:33:08 +0000 (12:33 -0700)
commit71ffd1dc5234f522a7647dd30ca8fc9eefe8da1b
tree3912b1756c2580a048c14766f56d1a8f395f583c
parentb41c1d8d07906786c60893980d52688f31d114a6
fscrypt: Don't use asynchronous CryptoAPI algorithms

Now that fscrypt's incomplete support for non-inline crypto engines has
been removed, and none of the CPU-based algorithms have the
CRYPTO_ALG_ASYNC flag set anymore, there is no need to accommodate
asynchronous algorithms.  Therefore, explicitly allocate only
synchronous algorithms.  Then, remove the code that handled waiting for
asynchronous en/decryption operations to complete.

This commit should *not* be backported to kernels that lack commit
0ba6ec5b2972 ("crypto: x86/aes - stop using the SIMD helper"), as then
it would disable the use of the optimized AES code on x86.

Link: https://lore.kernel.org/r/20250710060754.637098-2-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
fs/crypto/crypto.c
fs/crypto/fname.c
fs/crypto/fscrypt_private.h
fs/crypto/keysetup_v1.c