NFSD: Don't start lockd when only NFSv4 is running
authorKinglong Mee <kinglongmee@gmail.com>
Tue, 31 Dec 2013 05:17:30 +0000 (13:17 +0800)
committerJ. Bruce Fields <bfields@redhat.com>
Fri, 3 Jan 2014 23:18:50 +0000 (18:18 -0500)
commit8ef667140c52e9b88934664954217f28559c75d6
tree73d4f73af96dad3d92af96a9086f3b354ab79799
parent7e55b59b2f32afc83452ae250dfd6173c9a7b515
NFSD: Don't start lockd when only NFSv4 is running

When starting without nfsv2 and nfsv3, nfsd does not need to start
lockd (and certainly doesn't need to fail because lockd failed to
register with the portmapper).

Reported-by: Gareth Williams <gareth@garethwilliams.me.uk>
Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/netns.h
fs/nfsd/nfssvc.c