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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
