Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030235Ab2HWIGz (ORCPT ); Thu, 23 Aug 2012 04:06:55 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:39667 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933677Ab2HWIGd (ORCPT ); Thu, 23 Aug 2012 04:06:33 -0400 Date: Thu, 23 Aug 2012 12:06:27 +0400 From: Cyrill Gorcunov To: "Aneesh Kumar K.V" Cc: Pavel Emelyanov , "J. Bruce Fields" , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , Al Viro , Alexey Dobriyan , Andrew Morton , James Bottomley , Matthew Helsley Subject: Re: [patch 4/8] fs, exportfs: Add export_encode_inode_fh helper Message-ID: <20120823080627.GA1992@moon> References: <20120815092409.591460800@openvz.org> <87fw7habo4.fsf@skywalker.in.ibm.com> <20120820163338.GN23596@moon> <20120820183225.GB4911@fieldses.org> <20120820190606.GE27443@moon> <20120820193204.GD5779@fieldses.org> <50335261.5090504@parallels.com> <87wr0sle4v.fsf@skywalker.in.ibm.com> <503367CB.9080609@parallels.com> <87zk5nsch8.fsf@skywalker.in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87zk5nsch8.fsf@skywalker.in.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1275 Lines: 37 On Wed, Aug 22, 2012 at 11:19:07AM +0530, Aneesh Kumar K.V wrote: > Pavel Emelyanov writes: > > > Why? For e.g. ext4 you can construct a handle in userspace and open by > > it. > > open_by_handle use exportfs_decode_fh which use file system specific > fh_to_dentry > > foe ext4 we require a generation number > > inode = get_inode(sb, fid->i32.ino, fid->i32.gen); > Hi Aneesh, yes we need i_generation but for ext3/4 it could be fetched with ioctl as far as i see. > For brtfs > > objectid = fid->objectid; > root_objectid = fid->root_objectid; > generation = fid->gen; > > return btrfs_get_dentry(sb, objectid, root_objectid, generation, 1); For btrfs it become more complex. But still the last version I'm about to send for review today (once everything get tested) will provide fhandle carried with inotify mark _and_ inode number and device. This information should be enough for us. After all having inode and device should allow us to figure out the fs used on inotify target. Cyrill -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/