.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
-.TH FANOTIFY 7 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH FANOTIFY 7 2014-12-31 "Linux" "Linux Programmer's Manual"
.SH NAME
fanotify \- monitoring filesystem events
.SH DESCRIPTION
The event queue can overflow.
In this case, events are lost.
.SH BUGS
-As of Linux 3.15,
+As of Linux 3.17,
the following bugs exist:
.IP * 3
+On Linux, a filesystem object may be accessible through multiple paths,
+for example, a part of a filesystem may be remounted using the
+.IR \-\-bind
+option of
+.BR mount (8).
+A listener that marked a mount will be notified only of events that were
+triggered for a filesystem object using the same mount.
+Any other event will pass unnoticed.
+.IP *
+Calling
+.BR fallocate (2)
+does not create any fanotify events.
+.IP *
.\" FIXME . A patch was proposed.
When an event is generated,
no check is made to see whether the user ID of the
file descriptor */
if (fanotify_mark(fd, FAN_MARK_ADD | FAN_MARK_MOUNT,
- FAN_OPEN_PERM | FAN_CLOSE_WRITE, \-1,
+ FAN_OPEN_PERM | FAN_CLOSE_WRITE, AT_FDCWD,
argv[1]) == \-1) {
perror("fanotify_mark");
exit(EXIT_FAILURE);
.BR fanotify_mark (2),
.BR inotify (7)
.SH COLOPHON
-This page is part of release 3.75 of the Linux
+This page is part of release 3.76 of the Linux
.I man-pages
project.
A description of the project,