From owner-cvs-all Wed Sep 29 10:16:56 1999 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BEC9515938; Wed, 29 Sep 1999 10:14:59 -0700 (PDT) (envelope-from dillon@FreeBSD.org) Received: (from dillon@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA70728; Wed, 29 Sep 1999 10:14:59 -0700 (PDT) (envelope-from dillon@FreeBSD.org) Message-Id: <199909291714.KAA70728@freefall.freebsd.org> From: Matt Dillon Date: Wed, 29 Sep 1999 10:14:59 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/nfs nfs_serv.c Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk dillon 1999/09/29 10:14:59 PDT Modified files: sys/nfs nfs_serv.c Log: 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. Revision Changes Path 1.86 +5 -1 src/sys/nfs/nfs_serv.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message