Messages in this thread | | | From | Arnd Bergmann <> | Subject | Re: [take 3] Use pid in inotify events. | Date | Fri, 21 Nov 2008 19:39:45 +0100 |
| |
On Friday 21 November 2008, Evgeniy Polyakov wrote: > I have a network server, which gets IO requests from different clients > and maintains coherency of the data between them, but if file is > modified locally I want to flush or invalidate remote data. I decided > not to dig into the kernel on the server node and use inotify to get > notifications about events, but there is no way to determine if given IO > was originated by server itself (and in this case nothing should be > done), or by external application which accesses exported directory (and > in this case I should send update messages to clients).
The how about an inotify_init1 flag telling the kernel to ignore changes done by the current PID? That sounds like it is potentially useful to other applications that want to monitor the whole file system and also write to it. It also doesn't need to change the ABI in incompatible ways or introduce a security relevant side channel.
Arnd <><
| |