On Mon, Aug 20, 2012 at 03:32:04PM -0400, J. Bruce Fields wrote: > > > > Hi, sorry for dealy. Well, the last idea is to get rid of this helper, > > > > I've sent out an updated version where ino+dev is only printed. > > > > > > I don't understand how ino and dev are useful to you, though, if you're > > > still hoping to be able to look up inodes using this information later > > > on. > > > > Hi Bruce, I believe having ino+dev is better than nothing. Otherwise we > > simply have no clue which targets are bound to inotify mark. Sometime > > (!) we can try to generate fhandle in userspace from this ino+dev bundle > > and then open the target file. > > That's insufficient to generate a filehandle in general. That's why I said `sometime', and this is better than nothing. > (Also: there's the usual inode-number aliasing problem: the inode number > could get reused by another file. Unless you know the file is being > held open the whole time.) For c/r session inode should exist and not get reused. 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
