Eric Paris cb2d429faf fsnotify: add group priorities ... This introduces an ordering to fsnotify groups. With purely asynchronous notification based "things" implementing fsnotify (inotify, dnotify) ordering isn't particularly important. But if people want to use fsnotify for the basis of sycronous notification or blocking notification ordering becomes important. eg. A Hierarchical Storage Management listener would need to get its event before an AV scanner could get its event (since the HSM would need to bring the data in for the AV scanner to scan.) Typically asynchronous notification would want to run after the AV scanner made any relevant access decisions so as to not send notification about an event that was denied. Signed-off-by: Eric Paris <eparis@redhat.com>		2010-07-28 09:59:01 -04:00
..
fanotify_user.c	fsnotify: add group priorities	2010-07-28 09:59:01 -04:00
fanotify.c	fanotify: ignored_mask to ignore events	2010-07-28 09:59:00 -04:00
Kconfig	fanotify: select ANON_INODES.	2010-07-28 09:58:56 -04:00
Makefile	fanotify: fanotify_init syscall declaration	2010-07-28 09:58:55 -04:00