iedowse aeec108485 In the NFSv3 `fsinfo' procedure reply, don't claim that we support ... 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 <lihtnes78@netscape.net> Reviewed by: dillon Approved by: re MFC-after: 1 week		2002-12-05 16:58:11 +00:00
..
nfs_serv.c	In the NFSv3 `fsinfo' procedure reply, don't claim that we support	2002-12-05 16:58:11 +00:00
nfs_srvcache.c	Add IPv6 support.	2002-07-15 19:40:23 +00:00
nfs_srvsock.c	Stick a dark comment in about the fact that the NFS server code allocates	2002-07-24 14:24:16 +00:00
nfs_srvsubs.c	- Introduce a new macro, since that's what nfs loves, called	2002-10-31 22:35:03 +00:00
nfs_syscalls.c	Permit MAC policies to instrument the access control decisions for	2002-11-04 15:13:36 +00:00
nfs.h	Fully exterminate nfsd_srvargs and nfsd_cargs. They were either unused	2002-07-24 22:27:35 +00:00
nfsm_subs.h	- Introduce a new macro, since that's what nfs loves, called	2002-10-31 22:35:03 +00:00
nfsrvcache.h
nfsrvstats.h