Calling fallocate.2 does not result in inotify events. Signed-off-by: Heinrich Schuchardt <xypron.glpk@xxxxxx> --- man7/inotify.7 | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/man7/inotify.7 b/man7/inotify.7 index a0e2528..7f45ba9 100644 --- a/man7/inotify.7 +++ b/man7/inotify.7 @@ -752,6 +752,10 @@ and also the possibility that there may not be any .B IN_MOVED_TO event. .SH BUGS +As of kernel 3.17, calling +.BR fallocate (2) +does not create any inotify events. + .\" FIXME . kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321 .\" implies that unmount events were buggy 2.6.11 to 2.6.36 .\" -- 2.1.0 -- 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
