From owner-freebsd-hackers Mon Jul 7 10:39:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26069 for hackers-outgoing; Mon, 7 Jul 1997 10:39:50 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26061 for ; Mon, 7 Jul 1997 10:39:45 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id TAA22123; Mon, 7 Jul 1997 19:39:00 +0200 Message-ID: <33C129B4.41C67EA6@bonn-online.com> Date: Mon, 07 Jul 1997 19:39:00 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Terry Lambert CC: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707022052.NAA08047@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I have now started exploring the vfs/nfs kernel code. It appears to me that maybe some things we need for the fcntl(F_CNVT) call are already there. Namely, the nfsrv_fhtovp() function in nfs/nfs_subs.c converts a file handle (fhandle_t, not struct fid) into a vnode. So one could possibly use this function (or a modified version) to create the vnode from the handle, use falloc() to create an open file and then tie the vnode to the file struct. Question is, is the fhandle_t the same as the nfs file handle? This is only guesswork, since I am absolutely no kernel programming expert. Am I thinking in the right direction? Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com