From owner-freebsd-hackers  Wed Apr 14  0:53:26 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 522D314ED5
	for <hackers@freebsd.org>; Wed, 14 Apr 1999 00:53:24 -0700 (PDT)
	(envelope-from will@ns.oeno.com)
Received: (qmail 12743 invoked by uid 1001); 14 Apr 1999 07:51:03 -0000
Date: 14 Apr 1999 07:51:03 -0000
Message-ID: <19990414075103.12740.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: thorpej@nas.nasa.gov
Cc: hackers@freebsd.org
In-reply-to: <199904131616.JAA20900@lestat.nas.nasa.gov> (message from Jason
	Thorpe on Tue, 13 Apr 1999 09:16:07 -0700)
Subject: Re: read() and pread() syscalls
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>  > I don't have a NetBSD machine around, but it might apply to NetBSD, as
>  > well, unless NetBSD keeps the vnode exclusively locked for the entire
>  > duration of a VOP_READ, even if it blocks.
> 
> There is no need to keep the _vnode_ locked; the file offset is not stored
> in the vnode, but in the struct file that references that vnode.

Of course, but my assumption was that current *BSD code does not make
any explicit attempts to protect f_offset and that it might, in some
cases, be protected as a side-effect of vnode locking.


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