src-test2/sys/nfsserver, branch releng/5.0

In the NFSv3 `fsinfo' procedure reply, don't claim that we support

2002-12-05T16:58:11Z

32k read and write operations on datagram sockets when in fact we reject requests larger than 16k. It must be the case that virtually all clients use data sizes of 16k or less for UDP transport (FreeBSD's client defaults to 8k and never exceeds 16k), as this bug has been present ever since NFSv3 support was added. Reported by: Senthil Reviewed by: dillon Approved by: re MFC-after: 1 week

Permit MAC policies to instrument the access control decisions for

2002-11-04T15:13:36Z

system accounting configuration and for nfsd server thread attach. Policies might use this to protect the integrity or confidentiality of accounting data, limit the ability to turn on or off accounting, as well as to prevent inappropriately labeled threads from becoming nfs server threads. Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories

- Introduce a new macro, since that's what nfs loves, called

2002-10-31T22:35:03Z

nfsm_srvpathsiz. This macro plucks a length out of an rpc request and verifies that its size does not exceed NFS_MAXPATHLEN. If it does it generates an ENAMETOOLONG response. - Use this macro, and the existing nfsm_srvnamsiz macro in two places where we deal with paths passed in by the client. This fixes a linux interoperability bug. Linux was sending oversized path components which would cause us to ignore the request all together. This causes linux to hang indefinitly while it waits for a response. This could still happen in other cases where we error out with EBADRPC. Sponsored by: Isilon Systems, Inc. Reviewed by: alfred, fabbri@isilon.com, neal@isilon.com

Set the NOMACCHECK flag for namei()'s generated by the NFS server code.

2002-10-19T21:27:40Z

We currently don't enforce protections on NFS-originated VOP's. Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories

Correct a problem wherein NFS servers running NFSv2 would not return

2002-10-03T21:50:37Z

certain classes of failure responses to the client during a failed remove operation. Submitted by: Ian Dowse

- Use incore() instead of gbincore() so we don't have to acquire the

2002-09-25T02:39:39Z

vnode interlock.

Use m_length() instead of home-rolled versions.

2002-09-18T19:44:14Z

Make the V2 errno translation more resistent to new errnos.

2002-08-21T19:28:44Z

- Replace v_flag with v_iflag and v_vflag

2002-08-04T10:29:36Z

- v_vflag is protected by the vnode lock and is used when synchronization with VOP calls is needed. - v_iflag is protected by interlock and is used for dealing with vnode management issues. These flags include X/O LOCK, FREE, DOOMED, etc. - All accesses to v_iflag and v_vflag have either been locked or marked with mp_fixme's. - Many ASSERT_VOP_LOCKED calls have been added where the locking was not clear. - Many functions in vfs_subr.c were restructured to provide for stronger locking. Idea stolen from: BSD/OS

Oops, another unused arg to nfssvc_nfsd(). blush

2002-07-24T23:10:34Z

Submitted by: jake