src/sys/modules/nfsclient, branch releng/10.2FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F10.22011-04-25T22:22:51ZFix the experimental NFS client so that it does not bogusly2011-04-25T22:22:51ZRick Macklemrmacklem@FreeBSD.org2011-04-25T22:22:51Zurn:sha1:7c208ed659437ef984f2bb98bdc20fa5cfdebefc
set the f_flags field of "struct statfs". This had the interesting
effect of making the NFSv4 mounts "disappear" after r221014,
since NFSMNT_NFSV4 and MNT_IGNORE became the same bit.
Move the files used for a diskless NFS root from sys/nfsclient
to sys/nfs in preparation for them to be used by both NFS
clients. Also, move the declaration of the three global data
structures from sys/nfsclient/nfs_vfsops.c to sys/nfs/nfs_diskless.c
so that they are defined when either client uses them.
Reviewed by: jhb
MFC after: 2 weeks
Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate2010-07-24T22:11:11ZRick Macklemrmacklem@FreeBSD.org2010-07-24T22:11:11Zurn:sha1:f92bbff2481ab999e7fec098d7c232779df7aa73
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
Factor out the code shared between NFS client and server into its own2010-02-16T20:00:21ZMarius Stroblmarius@FreeBSD.org2010-02-16T20:00:21Zurn:sha1:b06b8fe3a7842b556532ae3244a4cdca00cf5807
module. With r203732 it became apparent that creating the sysctl nodes
twice causes at least a warning, however the whole code shouldn't be
present twice in the first place.
Discussed with: rmacklem
EXPORT_SYMS is not, in fact, required, for a dependent module to access2009-10-13T09:21:20ZRobert Watsonrwatson@FreeBSD.org2009-10-13T09:21:20Zurn:sha1:03ce247827c59ed64331407c8f4d638d3e8facea
non-static symbols in a module they depend on, so remove dtrace symbols
from nfsclient's EXPORT_SYMS again.
Suggested by: jhb
Export DTrace symbols from nfsclient so that dtnfsclient can get to them.2009-10-12T18:59:31ZRobert Watsonrwatson@FreeBSD.org2009-10-12T18:59:31Zurn:sha1:99b5e2f1d2bfd9e1504197f67664b802eac5b503
This fixes DTrace with nfsclient built as a module.
MFC after: 3 days
Reported by: markm
Remove the old kernel RPC implementation and the NFS_LEGACYRPC option.2009-06-30T19:03:27ZDoug Rabsondfr@FreeBSD.org2009-06-30T19:03:27Zurn:sha1:b49a2b39fdac2fd3489a6e579946c87104a51f33
Approved by: re
After r193232 rt_tables in vnet.h are no longer indirectly dependent on2009-06-08T19:57:35ZBjoern A. Zeebbz@FreeBSD.org2009-06-08T19:57:35Zurn:sha1:8d8bc0182ea6f8f85409e76e53053487c7d23a84
the ROUTETABLES kernel option thus there is no need to include opt_route.h
anymore in all consumers of vnet.h and no longer depend on it for module
builds.
Remove the hidden include in flowtable.h as well and leave the two
explicit #includes in ip_input.c and ip_output.c.
Remove the unmaintained University of Michigan NFSv4 client from 8.x2009-05-22T12:35:12ZRobert Watsonrwatson@FreeBSD.org2009-05-22T12:35:12Zurn:sha1:86ce6a83d16fdedede88990ffe1d85ad83d8e7c8
prior to 8.0-RELEASE. Rick Macklem's new and more feature-rich NFSv234
client and server are replacing it.
Discussed with: rmacklem
Add opt_kdtrace.h to fix standalone module build.2009-04-06T20:17:28ZJohn Baldwinjhb@FreeBSD.org2009-04-06T20:17:28Zurn:sha1:6e57ff1890a629e39d2d24280626d6b6e362be76Rather than using hidden includes (with cicular dependencies),2008-12-02T21:37:28ZBjoern A. Zeebbz@FreeBSD.org2008-12-02T21:37:28Zurn:sha1:4b79449e2fb67cb37c4c9f46d31791893a39ddd8
directly include only the header files needed. This reduces the
unneeded spamming of various headers into lots of files.
For now, this leaves us with very few modules including vnet.h
and thus needing to depend on opt_route.h.
Reviewed by: brooks, gnn, des, zec, imp
Sponsored by: The FreeBSD Foundation