summaryrefslogtreecommitdiff
path: root/fs/jffs2/Kconfig
diff options
context:
space:
mode:
authorAmir Goldstein <amir73il@gmail.com>2018-04-04 23:42:18 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-04-24 10:36:38 +0300
commit28f46dee49d3eac6dbeac3e4c9ecf1b861d2594b (patch)
treec1ff66ed0b9a7adde0fe27ccd6d437031832f545 /fs/jffs2/Kconfig
parenta2a9d0190f9964dd734348085c22582e519c145a (diff)
downloadlinux-28f46dee49d3eac6dbeac3e4c9ecf1b861d2594b.tar.xz
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: 1968f5eed54c ("fanotify: use both marks when possible") Cc: stable <stable@vger.kernel.org> Signed-off-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/jffs2/Kconfig')
0 files changed, 0 insertions, 0 deletions