8cb6b1bae2
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> |
||
---|---|---|
.. | ||
nfs_serv.c | ||
nfs_srvcache.c | ||
nfs_srvsock.c | ||
nfs_srvsubs.c | ||
nfs_syscalls.c | ||
nfs.h | ||
nfsm_subs.h | ||
nfsproto.h | ||
nfsrvcache.h | ||
nfsrvstats.h |