From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: mtk.manpages@gmail.com, Jan Kara <jack@suse.cz>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
linux-man@vger.kernel.org
Subject: Re: [PATCH 2/4] fanotify_mark.2: Clarification about FAN_EVENT_ON_CHILD and new events
Date: Mon, 20 Apr 2020 21:03:17 +0200 [thread overview]
Message-ID: <db43d178-b9b4-59a2-10dc-9a4d0c7fe642@gmail.com> (raw)
In-Reply-To: <20200420184259.29406-3-amir73il@gmail.com>
Hello Amir,
On 4/20/20 8:42 PM, Amir Goldstein wrote:
> 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@gmail.com>
> Reviewed-by: Jan Kara <jack@suse.cz>
> Reviewed-by: Matthew Bobrowski <mbobrowski@mbobrowski.org>
Thanks. Patch applied.
Cheers,
Michael
> ---
> 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
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-04-20 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 18:42 [PATCH 0/4] fanotify updates for v5.7 Amir Goldstein
2020-04-20 18:42 ` [PATCH 1/4] fanotify_mark.2: Clarification about FAN_MARK_MOUNT and FAN_REPORT_FID Amir Goldstein
2020-04-20 19:00 ` Michael Kerrisk (man-pages)
2020-04-20 18:42 ` [PATCH 2/4] fanotify_mark.2: Clarification about FAN_EVENT_ON_CHILD and new events Amir Goldstein
2020-04-20 19:03 ` Michael Kerrisk (man-pages) [this message]
2020-04-20 18:42 ` [PATCH 3/4] fanotify.7: Fix fanotify_fid.c example Amir Goldstein
2020-04-20 19:06 ` Michael Kerrisk (man-pages)
2020-04-20 18:42 ` [PATCH 4/4] fanotify.7, fanotify_mark.2: Document FAN_DIR_MODIFY Amir Goldstein
2020-04-20 19:25 ` Michael Kerrisk (man-pages)
2020-04-20 19:36 ` [PATCH 0/4] fanotify updates for v5.7 Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db43d178-b9b4-59a2-10dc-9a4d0c7fe642@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-man@vger.kernel.org \
--cc=mbobrowski@mbobrowski.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).