Amir Goldstein 2e71b03423 fanotify: fix logic of events on child ... commit 54a307ba8d3cd00a3902337ffaae28f436eeb1a4 upstream. When event on child inodes are sent to the parent inode mark and parent inode mark was not marked with FAN_EVENT_ON_CHILD, the event will not be delivered to the listener process. However, if the same process also has a mount mark, the event to the parent inode will be delivered regadless of the mount mark mask. This behavior is incorrect in the case where the mount mark mask does not contain the specific event type. For example, the process adds a mark on a directory with mask FAN_MODIFY (without FAN_EVENT_ON_CHILD) and a mount mark with mask FAN_CLOSE_NOWRITE (without FAN_ONDIR). A modify event on a file inside that directory (and inside that mount) should not create a FAN_MODIFY event, because neither of the marks requested to get that event on the file. Fixes: 1968f5eed5 ("fanotify: use both marks when possible") Signed-off-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Jan Kara <jack@suse.cz> [bwh: Backported to 3.16: adjust context] Signed-off-by: Ben Hutchings <ben@decadent.org.uk>		2019-07-27 21:52:17 +02:00
..
dnotify	new helper: file_inode(file)	2013-02-22 23:31:31 -05:00
fanotify	fanotify: fix logic of events on child	2019-07-27 21:52:17 +02:00
inotify	vfs: Add permission2 for filesystems with per mount permissions	2018-02-06 13:12:19 +01:00
fdinfo.c	fs/notify: don't show f_handle if exportfs_encode_inode_fh failed	2014-10-05 14:54:13 -07:00
fdinfo.h
fsnotify.c	BACKPORT: dentry name snapshots	2017-12-22 20:25:56 +00:00
fsnotify.h
group.c
inode_mark.c	fsnotify: next_i is freed during fsnotify_unmount_inodes.	2015-01-27 07:52:33 -08:00
Kconfig
Makefile
mark.c	fsnotify: fix oops in fsnotify_clear_marks_by_group_flags()	2015-12-24 14:46:16 +05:30
notification.c
vfsmount_mark.c	hlist: drop the node parameter from iterators	2013-02-27 19:10:24 -08:00