fscrypt: Don't use asynchronous CryptoAPI algorithms

Browse source

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
0ba6ec5b29 ("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>

...

This commit is contained in:

Eric Biggers 2025-07-09 23:07:48 -07:00

parent b41c1d8d07

commit 71ffd1dc52

4 changed files with 18 additions and 21 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

7

fs/crypto/crypto.c

View file

18

fs/crypto/fname.c

View file

5

fs/crypto/fscrypt_private.h

View file

9

fs/crypto/keysetup_v1.c

View file