2012/1/7 Al Viro <viro@xxxxxxxxxxxxxxxxxx>: > On Sat, Jan 07, 2012 at 02:36:12PM +0100, Stef Bon wrote: >> from: Stef Bon >> watch has been set (by who, and where, which mask) and when removed >> (pid/fd/wd). > > And what, pray tell, is the recepient to do with the contents of that > packet? Pardon the bluntness, but how the hell is your FUSE fs > supposed to tell that pathname has anything to do with it, nevermind > telling which object would it relate to? Especially when it has > no way to tell at which locations the damn thing happens to be mounted > from the caller POV. About bluntness, yes I've received blunt reactions from you in the past. We're working on the same goal here, and nobody is trying to misbehave, sabotage or do other nasty things so please be a bit more gentle. Maybe I'm not that into the kernel programming as you, but that is not a reason to get rude. Futher, the FUSE fs knows it's own mountpoint. (ignore the submounts on a FUSE fs here), it can filter out the watches which are set on the fs. This is not so hard right? What problems with "no way to tell at which locations the damn thing happens to" you are pointing at?? (When another fs is mounted on a directory part of a FUSE fs this is making things complicated, but not impossible, the fs needs to have a table of all mounted filesystems to determine a watch is set on a inode part of the fs or of another fs). When it is set on an object part of the fs, the fs can then translate the path relative to the mountpoint to an inode used internally by the fs or any other reference used to identify objects. This has to exist. The FUSE fs can then set a backend specific watch on the inode, and report anything back to the kernel when anything "happens", using the fuse_lowlevel_notify_.. calls. I haven't tested this through and through, so I do not know yet the inotify subsystem will pick up the changes reported by the fuse_lowlevel_notify_.. calls. Stef Bon > > NAK. > -- > 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 -- 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
