From owner-freebsd-fs  Sun Jul 28 03:58:10 1996
Return-Path: owner-fs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA15339
          for fs-outgoing; Sun, 28 Jul 1996 03:58:10 -0700 (PDT)
Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA15334
          for <freebsd-fs@freebsd.org>; Sun, 28 Jul 1996 03:58:04 -0700 (PDT)
Received: from cent.cs.tu-berlin.de (loewis@cent.cs.tu-berlin.de [130.149.22.20]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id MAA05283 for <freebsd-fs@freebsd.org>; Sun, 28 Jul 1996 12:56:47 +0200
From: "Martin v.Loewis" <loewis@cs.tu-berlin.de>
Received: (loewis@localhost) by cent.cs.tu-berlin.de (8.6.12/8.6.6) id MAA18474 for freebsd-fs@freebsd.org; Sun, 28 Jul 1996 12:56:46 +0200
Message-Id: <199607281056.MAA18474@cent.cs.tu-berlin.de>
Subject: VGET question
To: freebsd-fs@freebsd.org
Date: Sun, 28 Jul 1996 12:56:45 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-fs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I wonder whether VOP_VGET should return the vnode locked. Most filesystems
check their hash lists, and if the vnode is there, they'll perform 
vget(vp,1), thus locking the vnode.
If they need a new vnode, they get it from getnewvnode, which returns it
unlocked. In all cases I've checked, the vnode is then return unlocked to
the caller.
So what is the proper behaviour, here?

Thanks,
Martin