Some of the new event types that were added in v5.1 along with init flag FAN_REPORT_FID are not eligable for reporting to a directory watching with FAN_EVENT_ON_CHILD. Document the events that cannot be generated on children of a watching parent. Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx> Reviewed-by: Jan Kara <jack@xxxxxxx> Reviewed-by: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx> --- man2/fanotify_mark.2 | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2 index 687e20f4a..7fbcd5e36 100644 --- a/man2/fanotify_mark.2 +++ b/man2/fanotify_mark.2 @@ -314,8 +314,21 @@ Events for the immediate children of marked directories shall be created. The flag has no effect when marking mounts and filesystems. Note that events are not generated for children of the subdirectories of marked directories. +More specifically, the directory entry modification events +.BR FAN_CREATE , +.BR FAN_DELETE , +.BR FAN_MOVED_FROM +and +.BR FAN_MOVED_TO +are not generated for any entry modifications performed inside subdirectories +of marked directories. +Note that the events +.BR FAN_DELETE_SELF +and +.BR FAN_MOVE_SELF +are not generated for children of marked directories. To monitor complete directory trees it is necessary to mark the relevant -mount. +mount or filesystem. .PP The following composed values are defined: .TP -- 2.17.1
