Hi all, This series is a prep work for using fanotify to monitor all events in a file system with a single watch. The end result is indented to be an alternative to the recursive inotify watches scheme, which has its problems. This first part adds support for most inotify events to fanotify when watching a directory. The next part will add support for watching a super block, which is not the same as watching a mount point. I am posting this WIP to get feedback on the idea and to find out if there are any users out there interested in the improved fanotify capabilities and/or in the super block monitoring use case. Amir Goldstein (7): fsnotify: pass dentry instead of inode when available fsnotify: annotate filename events fanotify: new init flag FAN_EVENT_INFO_PARENT fanotify: store mount point from which an inode watch was added fanotify: support events with data type FSNOTIFY_EVENT_DENTRY fanotify: add support for create/attrib/rename/delete events fanotify: pass filename info for filename events fs/notify/fanotify/fanotify.c | 85 +++++++++++++++++++++++++++++++---- fs/notify/fanotify/fanotify.h | 24 +++++++++- fs/notify/fanotify/fanotify_user.c | 92 ++++++++++++++++++++++++++++++++++---- fs/notify/fdinfo.c | 4 +- fs/notify/fsnotify.c | 2 +- fs/notify/inode_mark.c | 1 + fs/notify/mark.c | 15 +++++-- include/linux/fsnotify.h | 46 ++++++++++++++----- include/linux/fsnotify_backend.h | 24 +++++++--- include/uapi/linux/fanotify.h | 41 ++++++++++++++--- 10 files changed, 287 insertions(+), 47 deletions(-) -- 2.7.4 -- 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
