From owner-cvs-sys Wed Aug 14 02:03:26 1996 Return-Path: owner-cvs-sys Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA17297 for cvs-sys-outgoing; Wed, 14 Aug 1996 02:03:26 -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 CAA17282; Wed, 14 Aug 1996 02:03:20 -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 KAA16563; Wed, 14 Aug 1996 10:02:49 +0100 Date: Wed, 14 Aug 1996 10:02:48 +0100 (BST) From: Doug Rabson To: Julian Elischer cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/miscfs/devfs devfs_tree.c devfs_vnops.c In-Reply-To: <199608131948.MAA06002@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-sys@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 13 Aug 1996, Julian Elischer wrote: > julian 96/08/13 12:48:44 > > Modified: sys/miscfs/devfs devfs_tree.c devfs_vnops.c > Log: > Submitted by: doug Rabson (dfr@render.com) > cleaning up some of the vnode usage.. > > (I'm sure it still needs more..) > where can one find out what each vfs call expects to be locked > on completion, and how can one find out what each layer expects > to be freed on error.? That reminds me. I should commit my VFS(9) manpages soon. That should have most of the right information. I had to deduce the locking protocol by examining various filesystem source code but I think I got it right. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426