linux/fs/notify/fanotify
Amir Goldstein b469e7e47c fanotify: fix handling of events on child sub-directory
When an event is reported on a sub-directory and the parent inode has
a mark mask with FS_EVENT_ON_CHILD|FS_ISDIR, the event will be sent to
fsnotify() even if the event type is not in the parent mark mask
(e.g. FS_OPEN).

Further more, if that event happened on a mount or a filesystem with
a mount/sb mark that does have that event type in their mask, the "on
child" event will be reported on the mount/sb mark.  That is not
desired, because user will get a duplicate event for the same action.

Note that the event reported on the victim inode is never merged with
the event reported on the parent inode, because of the check in
should_merge(): old_fsn->inode == new_fsn->inode.

Fix this by looking for a match of an actual event type (i.e. not just
FS_ISDIR) in parent's inode mark mask and by not reporting an "on child"
event to group if event type is only found on mount/sb marks.

[backport hint: The bug seems to have always been in fanotify, but this
                patch will only apply cleanly to v4.19.y]

Cc: <stable@vger.kernel.org> # v4.19
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
2018-11-08 15:43:48 +01:00
..
Kconfig treewide: Fix typos in Kconfig 2017-10-12 15:42:00 +02:00
Makefile fanotify: fanotify_init syscall declaration 2010-07-28 09:58:55 -04:00
fanotify.c fanotify: fix handling of events on child sub-directory 2018-11-08 15:43:48 +01:00
fanotify.h fanotify: support reporting thread id instead of process id 2018-10-08 13:48:45 +02:00
fanotify_user.c fanotify: support reporting thread id instead of process id 2018-10-08 13:48:45 +02:00