From owner-freebsd-fs  Sat May 30 19:51:24 1998
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA17051
          for freebsd-fs-outgoing; Sat, 30 May 1998 19:51:24 -0700 (PDT)
          (envelope-from owner-freebsd-fs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17046
          for <fs@FreeBSD.ORG>; Sat, 30 May 1998 19:51:22 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA28948;
	Sun, 31 May 1998 12:42:38 +1000
Date: Sun, 31 May 1998 12:42:38 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199805310242.MAA28948@godzilla.zeta.org.au>
To: eivind@yes.no, fs@FreeBSD.ORG
Subject: Re: componentnames to VOPs
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>Is there any documentation as to whether these should be locked by
>namei() or not?

vnodes are locked by namei() according to the LOCKPARENT and LOCKLEAF
flags.  I don't know what you mean by locking a componentname.  If
the parent isn't locked, then the information in the componentname
may become stale.  Mostly you don't care.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message