From owner-freebsd-hackers  Mon May 31  6:18:22 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
	by hub.freebsd.org (Postfix) with SMTP id 5445114F09
	for <hackers@freebsd.org>; Mon, 31 May 1999 06:18:15 -0700 (PDT)
	(envelope-from will@ns.oeno.com)
Received: (qmail 21875 invoked by uid 1001); 31 May 1999 13:18:00 -0000
To: Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc: hackers@freebsd.org
Subject: Re: question about vnode and inode locking
References: <Pine.GSO.3.96.990530143132.15418A-100000@sol.cs.binghamton.edu>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 31 May 1999 16:15:57 +0300
In-Reply-To: zzhang@cs.binghamton.edu's message of "30 May 1999 21:51:55 +0300"
Message-ID: <86ogj1pegi.fsf@not.demophon.com>
Lines: 11
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


zzhang@cs.binghamton.edu (Zhihui Zhang) writes:

> It seems to me that we can lock at the vnode layer AND at the inode layer. 

No, the inode lock is, in most cases, the vnode layer lock.  It isn't
obvious because the code assumes that any filesystem using vop_stdlock
has a 'struct lock' as the first entry of the internal data pointed to
by v_data.

Very ugly.


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