2.6.39 nfsd and crypto =n
Subsystems (2)
During compile, I received this:
ERROR: "crypto_destroy_tfm" [fs/nfsd/nfsd.ko] undefined!
ERROR: "crypto_alloc_base" [fs/nfsd/nfsd.ko] undefined!
.config nfsd options:CONFIG_NFSD=m
# CONFIG_NFSD_DEPRECATED is not setCONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not setCONFIG_NFSD_V4=y
and crypto:
# CONFIG_CRYPTO is not set
making the following change fixes:
-# CONFIG_CRYPTO is not set
+CONFIG_CRYPTO=m
Should NFSD_V4 select CRYPTO? Should it select other things?
Signature · 2 lines
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22 million bugs.
PATCH 1/1 nfsd: v4 support requires CRYPTO
From: Randy Dunlap <[email protected]>
nfsd V4 support uses crypto interfaces, so select CRYPTO to fix build errors in 2.6.39:
ERROR: "crypto_destroy_tfm" [fs/nfsd/nfsd.ko] undefined!
ERROR: "crypto_alloc_base" [fs/nfsd/nfsd.ko] undefined!
--- fs/nfsd/Kconfig | 1 + 1 file changed, 1 insertion(+)
fs/nfsd/Kconfig +1 -0
@@ -82,6 +82,7 @@ config NFSD_V4 select NFSD_V3 select FS_POSIX_ACL select SUNRPC_GSS + select CRYPTO help This option enables support in your system's NFS server for version 4 of the NFS protocol (RFC 3530).
Re: [PATCH] nfsd: v4 support requires CRYPTO
Quoted 4 lines · Randy Dunlap
From: Randy Dunlap <[email protected]>
nfsd V4 support uses crypto interfaces, so select CRYPTO to fix build errors in 2.6.39:
Thanks, applying for 3.0.--b.
Quoted 21 lines
ERROR: "
crypto_destroy_tfm" [fs/nfsd/nfsd.ko] undefined!
ERROR: "crypto_alloc_base" [fs/nfsd/nfsd.ko] undefined!Reported-by Wakko Warner <[email protected]>Signed-off-by Randy Dunlap <[email protected]>--- fs/nfsd/Kconfig | 1 + 1 file changed, 1 insertion(+)fs/nfsd/Kconfig +1
-0@@ -82,6 +82,7 @@ config NFSD_V4 select NFSD_V3 select FS_POSIX_ACL select SUNRPC_GSS + select CRYPTO help This option enables support in your system's NFS server for version 4 of the NFS protocol (RFC 3530).