Eric Paris 4231a23530 fanotify: implement fanotify listener ordering ... The fanotify listeners needs to be able to specify what types of operations they are going to perform so they can be ordered appropriately between other listeners doing other types of operations. They need this to be able to make sure that things like hierarchichal storage managers will get access to inodes before processes which need the data. This patch defines 3 possible uses which groups must indicate in the fanotify_init() flags. FAN_CLASS_PRE_CONTENT FAN_CLASS_CONTENT FAN_CLASS_NOTIF Groups will receive notification in that order. The order between 2 groups in the same class is undeterministic. FAN_CLASS_PRE_CONTENT is intended to be used by listeners which need access to the inode before they are certain that the inode contains it's final data. A hierarchical storage manager should choose to use this class. FAN_CLASS_CONTENT is intended to be used by listeners which need access to the inode after it contains its intended contents. This would be the appropriate level for an AV solution or document control system. FAN_CLASS_NOTIF is intended for normal async notification about access, much the same as inotify and dnotify. Syncronous permissions events are not permitted at this class. Signed-off-by: Eric Paris <eparis@redhat.com>		2010-10-28 17:22:13 -04:00
..
fanotify_user.c	fanotify: implement fanotify listener ordering	2010-10-28 17:22:13 -04:00
fanotify.c	fanotify: drop duplicate pr_debug statement	2010-08-22 20:30:12 -04:00
Kconfig	fanotify: default Kconfig to n	2010-07-28 09:59:03 -04:00
Makefile	fanotify: fanotify_init syscall declaration	2010-07-28 09:58:55 -04:00