From: Stef B. <st...@gm...> - 2014-04-15 07:17:39
|
2014-04-14 17:24 GMT+02:00 Miklos Szeredi <mi...@sz...>: >> filesystems, fsnotify is not triggered by changes on the backend. > > So you want to change that? > Yes that's the idea. > That means first you have to add the infrastructure to fsnotify, in an > fs-independent manner (no explicit checks for "fuse" type). > Well if you look at the first patch, all is does (and as far I see is required) is call a fuse function if the fsnotify_mask is changed and the backend is a fuse fs. To complete this actually a config option (CONFIG_FSNOTIFY_FUSE) has to added I think. What do you mean with a " infrastructure to fsnotify, in an fs-independent manner"?? > Also, I'd start with just adding the notifications and then if that > all works then start allow notifications to be masked by what > userspace is actually watching. You mean first add the functions like fuse_lowlevel_notify_create? I thought about that, I started with the patches enabling fsnotify for fuse, but it's better to start with the notifications. Stef Bon |