Unfortunately fanotify does not inform listeners for all paths under which a touched file system object is visible but only the listener using the same path as the process touching the file system object. Signed-off-by: Heinrich Schuchardt <xypron.glpk@xxxxxx> --- man7/fanotify.7 | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/man7/fanotify.7 b/man7/fanotify.7 index bc5a11c..7f915c2 100644 --- a/man7/fanotify.7 +++ b/man7/fanotify.7 @@ -488,6 +488,14 @@ In this case, events are lost. As of Linux 3.17, the following bugs exist: .IP * 3 +On Linux a file system object may be accessible through multiple paths, +e.g. a part of the file system may be remounted using +.B mount (8) +--bind. +A listener that marked a mount will only be notified of events that were +triggered for a file system object using the same mount. +Any other event will pass unnoticed. +.IP * .\" FIXME . A patch was proposed. When an event is generated, no check is made to see whether the user ID of the -- 2.1.1 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
