Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753194Ab2HPPGg (ORCPT ); Thu, 16 Aug 2012 11:06:36 -0400 Received: from mailhub.sw.ru ([195.214.232.25]:38159 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750878Ab2HPPGe (ORCPT ); Thu, 16 Aug 2012 11:06:34 -0400 Message-ID: <502D0C6A.3010908@parallels.com> Date: Thu, 16 Aug 2012 19:06:18 +0400 From: Pavel Emelyanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1 MIME-Version: 1.0 To: Al Viro , Cyrill Gorcunov , "J. Bruce Fields" CC: James Bottomley , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , Alexey Dobriyan , Andrew Morton , Matthew Helsley Subject: Re: [patch 4/8] fs, exportfs: Add export_encode_inode_fh helper References: <20120816062448.GA32081@moon> <20120816123814.GD1209@moon> <20120816134339.GQ23464@ZenIV.linux.org.uk> <502CF9DA.8030701@parallels.com> <20120816135019.GS23464@ZenIV.linux.org.uk> <20120816135448.GP32081@moon> <1345125779.3259.50.camel@dabdike.int.hansenpartnership.com> <20120816141553.GF1209@moon> <20120816144152.GT23464@ZenIV.linux.org.uk> <20120816144835.GC13066@moon> <20120816145527.GU23464@ZenIV.linux.org.uk> In-Reply-To: <20120816145527.GU23464@ZenIV.linux.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1174 Lines: 28 On 08/16/2012 06:55 PM, Al Viro wrote: > On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote: > >>> Good luck doing that with e.g. VFAT... And then there's such thing >>> as filesystems that don't have ->encode_fh() for a lot of very good >> >> Wait, Al, it seems I messed up. If some fs has no encode_fh() implemented >> the default encoding with FILEID_INO32_GEN_PARENT will be used for that. > > ... which doesn't work for a lot of filesystems. Not if you want to be > able to decode the result afterwards and get something useful out of > that. Trying to implement ->fh_to_dentry(), especially with fhandle > generated by inode alone is going to be really interesting for a bunch > of stuff... > . > Hm... Then I suppose the best we can do is -- show in a fdinfo file the inode number, device where it is and a filehandle _iff_ provided by a filesystem. For fanotify/dnotify -- only a path. Thanks, Pavel -- 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/