wpaul a0ef521585 Correct the sanity test length calculation in nfsrv_readdirplus(): len is ... being incremented by 4 bytes too few each time through the loop, which allows more data into the mbuf chain that we really want. In the worst case, when we're using 32K read/write sizes with a TCP client, this causes readdirplus replies to sometimes exceed NFS_MAXPACKET which leads to a panic. This problem cropped up for me using an IRIX 6.5.4 NFSv3 TCP client with 32K read/write sizes, however supposedly it can be triggered by WinNT NFS servers too. In theory, it can probably be triggered by any NFS v3 implementation using TCP as long as it's using the maxiumum block size. Reviewed by: Matthew Dillon <dillon@backplane.com>		1999-07-29 21:42:57 +00:00
..
nfs_serv.c	Correct the sanity test length calculation in nfsrv_readdirplus(): len is	1999-07-29 21:42:57 +00:00
nfs_srvcache.c	Moved `#ifndef NFS_NOSERVER' after including nfs.h.	1998-07-02 12:41:42 +00:00
nfs_srvsock.c	Various changes lifted from the OpenBSD cvs tree:	1999-06-05 05:35:03 +00:00
nfs_srvsubs.c	I have not one single time remembered the name of this function correctly	1999-07-17 18:43:50 +00:00
nfs_syscalls.c	Matt's NFS fixes.	1999-06-23 04:44:14 +00:00
nfs.h	remove b_proc from struct buf, it's (now) unused.	1999-05-06 20:00:34 +00:00
nfsm_subs.h	Matt's NFS fixes.	1999-06-23 04:44:14 +00:00
nfsproto.h	For the on-the-wire protocol, u_long -> u_int32_t; long -> int32_t;	1998-05-31 20:09:01 +00:00
nfsrvcache.h	For the on-the-wire protocol, u_long -> u_int32_t; long -> int32_t;	1998-05-31 20:09:01 +00:00
nfsrvstats.h	remove b_proc from struct buf, it's (now) unused.	1999-05-06 20:00:34 +00:00