summaryrefslogtreecommitdiffstats
path: root/sys/nfsclient/nfs_vfsops.c
diff options
context:
space:
mode:
authorrmacklem <rmacklem@FreeBSD.org>2010-07-24 22:11:11 +0000
committerrmacklem <rmacklem@FreeBSD.org>2010-07-24 22:11:11 +0000
commitc7c4e3ebae85ae531fe298149a6ce0b2a0643a04 (patch)
tree4eec6454349918ebb035552eba42b0ef1fd7eaa6 /sys/nfsclient/nfs_vfsops.c
parent0dd9a760b4e6c729904b4821a46073d2840a105c (diff)
downloadFreeBSD-src-c7c4e3ebae85ae531fe298149a6ce0b2a0643a04.zip
FreeBSD-src-c7c4e3ebae85ae531fe298149a6ce0b2a0643a04.tar.gz
Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate
module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks
Diffstat (limited to 'sys/nfsclient/nfs_vfsops.c')
-rw-r--r--sys/nfsclient/nfs_vfsops.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/sys/nfsclient/nfs_vfsops.c b/sys/nfsclient/nfs_vfsops.c
index a4ef316..f07bf16 100644
--- a/sys/nfsclient/nfs_vfsops.c
+++ b/sys/nfsclient/nfs_vfsops.c
@@ -148,6 +148,7 @@ MODULE_DEPEND(nfs, krpc, 1, 1, 1);
MODULE_DEPEND(nfs, kgssapi, 1, 1, 1);
#endif
MODULE_DEPEND(nfs, nfs_common, 1, 1, 1);
+MODULE_DEPEND(nfs, nfslock, 1, 1, 1);
static struct nfs_rpcops nfs_rpcops = {
nfs_readrpc,
OpenPOWER on IntegriCloud