From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Xin Zhao" Subject: Where does NFS client associate the file handle received from server with inode? Date: Sat, 19 Aug 2006 21:36:57 -0400 Message-ID: <4ae3c140608191836we4603c0qa61d5631161a482d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from py-out-1112.google.com ([64.233.166.178]:29370 "EHLO py-out-1112.google.com") by vger.kernel.org with ESMTP id S932313AbWHTBg5 (ORCPT ); Sat, 19 Aug 2006 21:36:57 -0400 Received: by py-out-1112.google.com with SMTP id n25so1769997pyg for ; Sat, 19 Aug 2006 18:36:57 -0700 (PDT) To: linux-kernel , linux-fsdevel@vger.kernel.org Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org I ran into a problem: I extend several fields to file handle, and change compose_fh() to initialize some value into the file handle. I think the client side should be able to associate the file handle with inode and used them properly afterwards. However, I found a problem: Say I have a program 'postmark" in /tmp, and my current directory is / If I do '/tmp/postmark', getattr() funciton will not use the right file handle with extension. Instead, it seems to use a file handle excluding my extension but if I change to '/tmp', do 'ls -al' first, then I do 'postmark', getattr() will use the right file handle. So I think maybe I need to change NFS client to associate the extened file handle with inode . But I don't know where NFS client does this. Can someone give me a help? Many thanks! -x