Date: Mon, 2 Jul 2001 19:16:11 +0200 From: Nicolas Souchu <nsouch@fr.alcove.com> To: Doug Rabson <dfr@nlsystems.com> Cc: freebsd-hackers@freebsd.org Subject: Re: processes private data Message-ID: <20010702191611.A12009@avon.alcove-fr> In-Reply-To: <Pine.BSF.4.33.0106291329580.2969-100000@herring.nlsystems.com>; from dfr@nlsystems.com on Fri, Jun 29, 2001 at 01:34:19PM %2B0100 References: <20010629110607.B19935@avon.alcove-fr> <Pine.BSF.4.33.0106291329580.2969-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 29, 2001 at 01:34:19PM +0100, Doug Rabson wrote: > > When you get a new struct file from falloc(), VFS has nothing to do with > it. As you can see from the streamsopen() code, you can change f_ops > (which by default points at &badfileops) and f_data (defaults to zero) to > point at your own functions and data. > > The point is that you are creating a new file. The VFS-owned file which > ended up calling the open driver entrypoint will be discarded in favour of > your new one. But, what about all the locking stuff in vn_xxxx()? How can I know if I actually need them? Nicholas -- Alcôve Technical Manager - Nicolas.Souchu@fr.alcove.com - http://www.alcove.com Open Source Software Developer - nsouch@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010702191611.A12009>