Hi, earlier we spoke about making fs change notify work for cifs, nfs and fuse. I've contacted Jan Kara about this issue. I've explained that the big issue is how the fsevent calls can contact the different filesystems about the fact a watch has been set or removed. A callback/hook in fsnotify_add_inode_mark() and fsnotify_destroy_inode_mark() is required to make this work. The problem here that the original syscall should not wait for the setting of the watch has finished on the server, especially when dealing with a network fs. Maybe a special fsnotify queue per connection/mount is a good idea. The fsnotify callback for cifs will put a fs notify watch request on that queue, and signal the cifs process about it. What do you think? Stef -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
