Eric Paris 8112e2d6a7 fsnotify: include data in should_send calls ... fanotify is going to need to look at file->private_data to know if an event should be sent or not. This passes the data (which might be a file, dentry, inode, or none) to the should_send function calls so fanotify can get that information when available Signed-off-by: Eric Paris <eparis@redhat.com>		2010-07-28 09:58:31 -04:00
..
dnotify	fsnotify: include data in should_send calls	2010-07-28 09:58:31 -04:00
inotify	fsnotify: include data in should_send calls	2010-07-28 09:58:31 -04:00
fsnotify.c	fsnotify: include data in should_send calls	2010-07-28 09:58:31 -04:00
fsnotify.h	fsnotify: generic notification queue and waitq	2009-06-11 14:57:53 -04:00
group.c	fsnotify: kzalloc fsnotify groups	2010-07-28 09:58:20 -04:00
inode_mark.c	fsnotify: allow addition of duplicate fsnotify marks	2010-07-28 09:58:17 -04:00
Kconfig	fsnotify: use def_bool in kconfig instead of letting the user choose	2009-07-21 15:26:26 -04:00
Makefile	fsnotify: add marks to inodes so groups can interpret how to handle those inodes	2009-06-11 14:57:53 -04:00
notification.c	fsnotify: use kmem_cache_zalloc to simplify event initialization	2010-07-28 09:58:20 -04:00