diff options
| author | Herbert Xu <herbert@gondor.apana.org.au> | 2019-12-27 10:47:00 +0800 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2019-12-31 10:33:51 -0600 |
| commit | ede7a09fc8815011d67942e5b4a3cb1882b7bcd9 (patch) | |
| tree | 87a534a8a1d507c5944811c4a6d1df4e4c57515d /fs/ext4/Kconfig | |
| parent | e933adde6f97c4b51d39250c1dad0e89bd3fb1c7 (diff) | |
| download | linux-stable-ede7a09fc8815011d67942e5b4a3cb1882b7bcd9.tar.gz linux-stable-ede7a09fc8815011d67942e5b4a3cb1882b7bcd9.tar.bz2 linux-stable-ede7a09fc8815011d67942e5b4a3cb1882b7bcd9.zip | |
fscrypt: Allow modular crypto algorithms
The commit 643fa9612bf1 ("fscrypt: remove filesystem specific
build config option") removed modular support for fs/crypto. This
causes the Crypto API to be built-in whenever fscrypt is enabled.
This makes it very difficult for me to test modular builds of
the Crypto API without disabling fscrypt which is a pain.
As fscrypt is still evolving and it's developing new ties with the
fs layer, it's hard to build it as a module for now.
However, the actual algorithms are not required until a filesystem
is mounted. Therefore we can allow them to be built as modules.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Link: https://lore.kernel.org/r/20191227024700.7vrzuux32uyfdgum@gondor.apana.org.au
Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'fs/ext4/Kconfig')
| -rw-r--r-- | fs/ext4/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/ext4/Kconfig b/fs/ext4/Kconfig index ef42ab040905..db9bfa08d3e0 100644 --- a/fs/ext4/Kconfig +++ b/fs/ext4/Kconfig @@ -39,6 +39,7 @@ config EXT4_FS select CRYPTO select CRYPTO_CRC32C select FS_IOMAP + select FS_ENCRYPTION_ALGS if FS_ENCRYPTION help This is the next generation of the ext3 filesystem. |