summaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/inotify.txt
diff options
context:
space:
mode:
authorLino Sanfilippo <LinoSanfilippo@gmx.de>2015-02-10 14:08:27 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2015-02-10 14:30:28 -0800
commit66ba93c0d7fe63def447ad0afe380307ff9ebcad (patch)
treefc5cda114ac5c8b21688c83cd0b3e30cb218fb5b /Documentation/filesystems/inotify.txt
parentd2c1874ce687c175b544bc28b6187bf03735a931 (diff)
downloadtalos-obmc-linux-66ba93c0d7fe63def447ad0afe380307ff9ebcad.tar.gz
talos-obmc-linux-66ba93c0d7fe63def447ad0afe380307ff9ebcad.zip
fanotify: don't set FAN_ONDIR implicitly on a marks ignored mask
Currently FAN_ONDIR is always set on a mark's ignored mask when the event mask is extended without FAN_MARK_ONDIR being set. This may result in events for directories being ignored unexpectedly for call sequences like fanotify_mark(fd, FAN_MARK_ADD, FAN_OPEN | FAN_ONDIR , AT_FDCWD, "dir"); fanotify_mark(fd, FAN_MARK_ADD, FAN_CLOSE, AT_FDCWD, "dir"); Also FAN_MARK_ONDIR is only honored when adding events to a mark's mask, but not for event removal. Fix both issues by not setting FAN_ONDIR implicitly on the ignore mask any more. Instead treat FAN_ONDIR as any other event flag and require FAN_MARK_ONDIR to be set by the user for both event mask and ignore mask. Furthermore take FAN_MARK_ONDIR into account when set for event removal. [akpm@linux-foundation.org: coding-style fixes] Signed-off-by: Lino Sanfilippo <LinoSanfilippo@gmx.de> Reviewed-by: Jan Kara <jack@suse.cz> Cc: Eric Paris <eparis@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/filesystems/inotify.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud