On Thu, Aug 16, 2012 at 07:06:18PM +0400, Pavel Emelyanov wrote: > 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. For notifications on mount points it's not a problem (we already do that + ret = seq_printf(m, "fanotify mnt_id: %8x mask: %8x ignored_mask: %8x\n", + mnt->mnt_id, mark->mask, mark->ignored_mask); printing inode number and device it's easy as well. Fetching the path is not obvious for me since inotify carries inodes only. To generate path I would have to obtain dentry from inode I suppose, that's what you mean? Cyrill -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
