Hi.
So, it's time for the second version of the the fanotify
range patches.
The patch adds modification ranges to fsnotify events. Fanotify
is made to pass the range to the users.
This is useful for backup programs that work on huge files,
so that only a part of a modified file needs to be scanned
for changes.
changed. This is particularly useful for backup utilities that
work on huge files, so that only a part of the modified file
needs to be scanned for changes.
The series is split into 4 patches. The first one breaks the
ABI (but not API), and should get in before the .37 release,
or not at all. The last patch extends the ABI to handle event-
specific data ('options') in a backwards-compatible way.
You can also get the patchies from
git://git.zaytsev.su/git/linux-2.6.git branch fsnotify
A modified fanotify-example is available from
git://git.zaytsev.su/git/fanotify-example.git branch range
Changes since the first RFC:
1) Reworked the user interface, see the last patch.
2) Handle event merges properly.
3) Pass the range to fsnotify_parent().
3) Various small cleanups and fixes.
---
Alexey Zaytsev (4):
fanotify: Shrink struct fanotify_event_metadata by 32 bits
VFS: Tell fsnotify what part of the file might have changed
fsnotify: Handle the file change ranges
fanotify: Expose the file changes to the user
fs/compat.c | 2 -
fs/nfsd/vfs.c | 2 -
fs/notify/fanotify/fanotify.c | 19 +++++
fs/notify/fanotify/fanotify_user.c | 132 +++++++++++++++++++++++++++++++-----
fs/notify/fsnotify.c | 24 ++++---
fs/notify/inode_mark.c | 2 -
fs/notify/inotify/inotify_user.c | 2 -
fs/notify/notification.c | 18 ++++-
fs/open.c | 4 +
fs/read_write.c | 4 +
include/linux/fanotify.h | 88 +++++++++++++++++++++---
include/linux/fs.h | 14 ++++
include/linux/fsnotify.h | 68 +++++++++++--------
include/linux/fsnotify_backend.h | 31 +++++++-
14 files changed, 330 insertions(+), 80 deletions(-)
--
--
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
