Rick Macklem b76ec2db93 The name caching changes of r230394 exposed an intermittent bug ... in the new NFS server for NFSv4, where it would report ENOENT when the file actually existed on the server. This turned out to be caused by not initializing ni_topdir before calling lookup() and there was a rare case where the value on the stack location assigned to ni_topdir happened to be a pointer to a ".." entry, such that "dp == ndp->ni_topdir" succeeded in lookup(). This patch initializes ni_topdir to fix the problem. MFC after: 5 days		2012-03-03 16:13:20 +00:00
..
nfs_nfsdcache.c	hrs@ reported a panic to freebsd-stable@ under the subject line	2012-02-23 16:47:05 +00:00
nfs_nfsdkrpc.c
nfs_nfsdport.c	The name caching changes of r230394 exposed an intermittent bug	2012-03-03 16:13:20 +00:00
nfs_nfsdserv.c
nfs_nfsdsocket.c
nfs_nfsdstate.c
nfs_nfsdsubs.c