summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2019-12-04 07:13:22 +0100
committerJ. Bruce Fields <bfields@redhat.com>2019-12-07 17:28:52 +0100
commit38a2204f5298620e8a1c3b1dc7b831425106dbc0 (patch)
treedcf3016f7ed59361d3834905bedbf4b33101c722 /net
parentNFSD fixing possible null pointer derefering in copy offload (diff)
downloadlinux-38a2204f5298620e8a1c3b1dc7b831425106dbc0.tar.xz
linux-38a2204f5298620e8a1c3b1dc7b831425106dbc0.zip
nfsd: depend on CRYPTO_MD5 for legacy client tracking
The legacy client tracking infrastructure of nfsd makes use of MD5 to derive a client's recovery directory name. As the nfsd module doesn't declare any dependency on CRYPTO_MD5, though, it may fail to allocate the hash if the kernel was compiled without it. As a result, generation of client recovery directories will fail with the following error: NFSD: unable to generate recoverydir name The explicit dependency on CRYPTO_MD5 was removed as redundant back in 6aaa67b5f3b9 (NFSD: Remove redundant "select" clauses in fs/Kconfig 2008-02-11) as it was already implicitly selected via RPCSEC_GSS_KRB5. This broke when RPCSEC_GSS_KRB5 was made optional for NFSv4 in commit df486a25900f (NFS: Fix the selection of security flavours in Kconfig) at a later point. Fix the issue by adding back an explicit dependency on CRYPTO_MD5. Fixes: df486a25900f (NFS: Fix the selection of security flavours in Kconfig) Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions