diff options
| author | Aihua Zhang <zhangaihua1@huawei.com> | 2016-07-07 15:37:53 +0800 |
|---|---|---|
| committer | Miklos Szeredi <mszeredi@redhat.com> | 2016-09-16 12:44:20 +0200 |
| commit | f3fbbb079263bd29ae592478de6808db7e708267 (patch) | |
| tree | b34bc4b61e6993806773e4fa57ca26c2db63d9dc /fs/locks.c | |
| parent | 598e3c8f72f5b77c84d2cb26cfd936ffb3cfdbaa (diff) | |
| download | linux-f3fbbb079263bd29ae592478de6808db7e708267.tar.bz2 | |
fsnotify: support overlayfs
When an event occurs direct it to the overlay inode instead of the real
underlying inode.
This will work even if the file was first on the lower layer and then
copied up, while the watch is there. This is because the watch is on the
overlay inode, which stays the same through the copy-up.
For filesystems other than overlayfs this is a no-op, except for the
performance impact of an extra pointer dereferece.
Verified to work correctly with the inotify/fanotify tests in LTP.
Signed-off-by: Aihua Zhang <zhangaihua1@huawei.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Cc: Jan Kara <jack@suse.cz>
Cc: Eric Paris <eparis@redhat.com>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions