nfsd: Don't force CRYPTO_LIB_SHA256 to be built-in

Now that nfsd is accessing SHA-256 via the library API instead of via
crypto_shash, there is a direct symbol dependency on the SHA-256 code
and there is no benefit to be gained from forcing it to be built-in.
Therefore, select CRYPTO_LIB_SHA256 from NFSD (conditional on NFSD_V4)
instead of from NFSD_V4, so that it can be 'm' if NFSD is 'm'.

Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig
index 879e0b104d1c84cbdabdc42993bf52cf2ec11a48..e134dce45e350cde8b78bfac2dbed4b638d9ec7d 100644 (file)
--- a/fs/nfsd/Kconfig
+++ b/fs/nfsd/Kconfig
@@ -5,6 +5,7 @@ config NFSD
        depends on FILE_LOCKING
        depends on FSNOTIFY
        select CRC32
+       select CRYPTO_LIB_SHA256 if NFSD_V4
        select LOCKD
        select SUNRPC
        select EXPORTFS
@@ -77,7 +78,6 @@ config NFSD_V4
        select FS_POSIX_ACL
        select RPCSEC_GSS_KRB5
        select CRYPTO
-       select CRYPTO_LIB_SHA256
        select CRYPTO_MD5
        select GRACE_PERIOD
        select NFS_V4_2_SSC_HELPER if NFS_V4_2