summaryrefslogtreecommitdiffstats
path: root/sys/kern/vfs_syscalls.c
diff options
context:
space:
mode:
authordillon <dillon@FreeBSD.org>1999-09-29 17:14:58 +0000
committerdillon <dillon@FreeBSD.org>1999-09-29 17:14:58 +0000
commitaf7bbb9a33441701ff5146882af25965b2f6a467 (patch)
tree09639e910c57a0f9c7d7aa3f23c05f727a588b8f /sys/kern/vfs_syscalls.c
parent772404948c69414c95f54c1916194958d0c47172 (diff)
downloadFreeBSD-src-af7bbb9a33441701ff5146882af25965b2f6a467.zip
FreeBSD-src-af7bbb9a33441701ff5146882af25965b2f6a467.tar.gz
Make FreeBSD less conservative in determining when to return a cookie
error for a directory. I have made this change after a great deal of review although I cannot be absolutely sure that this meets the spec. The issue devolves into whether changes in an underlying (UFS) directory can cause NFS directory blocks to be renumbered. My read of the code indicates that NFS directory blocks will not be renumbered, which means that the cookies should still remain valid after a change is made to the underlying directory. This being the case, a cookie error should not be returned when a change is made to the underlying directory and, instead, the NFS client should rely on mtime detection to invalidate and reload the directory. The use of mtime is problematic in of itself, due to insufficient resolution, which is why I believe the original conservative error handling was done. Still, there have been dozens of bug reports by people needing solaris<->FreeBSD interoperability and these have to be accomodated.
Diffstat (limited to 'sys/kern/vfs_syscalls.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud