Since Linux 3.19 (820c12d5d6c0890bc93dd63893924a13041fdc35) fallocate.2 creates FAN_MODIFY and IN_MODIFY events. Signed-off-by: Heinrich Schuchardt <xypron.glpk@xxxxxx> --- man7/fanotify.7 | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/man7/fanotify.7 b/man7/fanotify.7 index 83d83c0..97402e1 100644 --- a/man7/fanotify.7 +++ b/man7/fanotify.7 @@ -485,7 +485,7 @@ Monitoring mounts offers the capability to monitor a whole directory tree. The event queue can overflow. In this case, events are lost. .SH BUGS -As of Linux 3.17, +As of Linux 4.0, the following bugs exist: .IP * 3 On Linux, a filesystem object may be accessible through multiple paths, @@ -497,10 +497,6 @@ 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 -- 2.1.4 -- 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
