On Fri, 2009-07-24 at 16:13 -0400, Eric Paris wrote: > I plan to start sending patches for fanotify in the next week or two. Generally, I appreciate your effort (as I'm sure does everyone else). I agree with Jamie that it's good to consider extending inotify and also that the special socket idea probably won't work for mainline. Also: 1). Ability to watch only certain mount-points, not just directories. Or directories and block on mount operations as Jamie suggested. Or both :) 2). Add event on mmap perhaps. Future theoretical cloud cuckoo land ideas include forcing all mmap operations to be read-only and then having the page fault handler fire an event for every write so that the anti-malware thing can monitor every single touched page...joke. 3). Sounds a lot like netlink could be close enough. Kay and others have been playing with in-kernel multiplexing and re-broadcasting of netlink events, and I'm pretty sure most of the rest is doable. I'm looking forward to updatedb using this. Let's try up-playing the use cases outside malware for this stuff. I think the average person is going to get more excited to see "Beagle done right" or "something like Microsoft indexer service"[0] than 1970s updatedb. It's certainly a nice and compelling reason to get this into mainline IMO. Jon. [0] Except anything but as crap as their version. Seriously, the last time I used a Windows system and looked at it, the indexer was consuming more CPU than Beagle ever did. And I liked the Beagle concept. -- 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
