From owner-freebsd-hackers Tue Oct 22 02:17:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA16399 for hackers-outgoing; Tue, 22 Oct 1996 02:17:54 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA16389 for ; Tue, 22 Oct 1996 02:17:41 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id JAA07492; Tue, 22 Oct 1996 09:55:40 +0100 Date: Tue, 22 Oct 1996 09:55:39 +0100 (BST) From: Doug Rabson Reply-To: Doug Rabson To: Terry Lambert cc: michaelh@cet.co.jp, karl@Mcs.Net, freebsd-hackers@FreeBSD.org Subject: Re: NFS node: disappearing directory In-Reply-To: <199610211747.KAA06162@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 21 Oct 1996, Terry Lambert wrote: > > > Depends on the FS. For NFS, "bogus cookie handling memory which was > > > allocated for fear the user buffer would be too small to return the > > > data". > > > > > > The problem is cookie related. The fix is to get rid of the cookie > > > code. > > > > The problem is cookie related but in the client. The cookie stuff Terry > > is going on about is in the server which is irrelavent to this bug. > > Correct me if I'm wrong, but real filesystems don't use the cookie > code: only the NFS server. > > If it's in the client code, how does this enter into it? The client is > a real FS... The NFS protocol uses the cookies themselves. The NFS client code speaks the NFS protocol and therefore *must* use cookies. It does *not* use the extra cookie interface to the VOP_READDIR call. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426