Messages in this thread | | | Date | Sun, 23 Nov 2008 21:08:05 -0800 | From | "John McCutchan" <> | Subject | Re: [take 3] Use pid in inotify events. |
| |
At this point I don't really want to see changes made to inotify. But, for arguments sake, why not something like inotify_init1 that takes a flag EXTENDED_EVENT which causes a larger event structure to be used. Something like,
struct inotify_event_extended { s32 wd; u32 mask; u32 cookie; u32 data[4]; char path[0]; }
The data array could be used to store arbitrary extra information, specified by flags.
On Sat, Nov 22, 2008 at 1:37 AM, Evgeniy Polyakov <zbr@ioremap.net> wrote: > On Fri, Nov 21, 2008 at 07:39:45PM +0100, Arnd Bergmann (arnd@arndb.de) wrote: >> 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. > > That's a good idea. Robert, John, Michael - comments? > > -- > Evgeniy Polyakov >
-- John McCutchan <john@johnmccutchan.com>
| |