From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
linux-man@vger.kernel.org
Subject: Re: [PATCH 1/3] fanotify.7, fanotify_mark.2: Generalize documentation of FAN_REPORT_FID
Date: Tue, 25 Aug 2020 09:50:48 +1000 [thread overview]
Message-ID: <20200824235048.GA29428@mail.bobrowski.net> (raw)
In-Reply-To: <20200824080326.5012-2-amir73il@gmail.com>
On Mon, Aug 24, 2020 at 11:03:24AM +0300, Amir Goldstein wrote:
> With fanotify_init(2) flag FAN_REPORT_FID, the group identifies
> filesystem objects by file handles in a single event info record of type
> FAN_EVENT_INFO_TYPE_FID.
>
> We indend to add support for new fanotify_init(2) flags for which the
> group identifies filesystem objects by file handles and add more event
> info record types.
>
> To that end, start by changing the language of the man page to refer
> to a "group that identifies filesystem objects by file handles" instead
> of referring to the FAN_REPORT_FID flag and document the extended event
> format structure in a more generic manner that allows more than a single
> event info record and not only a record of type FAN_EVENT_INFO_TYPE_FID.
>
> Clarify that the object identified by the file handle refers to the
> directory in directory entry modification events.
>
> Remove a note about directory entry modification events and monitoring
> a mount point that I found to be too confusing and out of context.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
...
> diff --git a/man7/fanotify.7 b/man7/fanotify.7
> index a7d60b2b9..a7b219168 100644
> --- a/man7/fanotify.7
> +++ b/man7/fanotify.7
> @@ -110,13 +110,11 @@ Two types of events are generated:
> events and
> .I permission
> events.
> -Notification events are merely informative
> -and require no action to be taken by
> -the receiving application with the exception being that the file
> -descriptor provided within a generic event must be closed.
> -The closing of file descriptors for each event applies only to
> -applications that have initialized fanotify without using
> -.BR FAN_REPORT_FID
> +Notification events are merely informative and require no action to be taken
> +by the receiving application with one exception - if a valid file descriptor
> +is provided within a generic event, the file descriptor must be closed.
Changes read well up until this point.
> +File descriptors are not provided with event to applications that have
> +created fanotify group so that it identifies filesystem objects by file handles
> (see below).
Then there's this sentence, which doesn't really read overly smoothly
as if there was a few words missing or something. Or, quite possibly
it's just me not understanding something?
/M
next prev parent reply other threads:[~2020-08-24 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 8:03 [PATCH 0/3] Fanotify man page updates for v5.9 Amir Goldstein
2020-08-24 8:03 ` [PATCH 1/3] fanotify.7, fanotify_mark.2: Generalize documentation of FAN_REPORT_FID Amir Goldstein
2020-08-24 9:49 ` Jan Kara
2020-08-24 23:50 ` Matthew Bobrowski [this message]
2020-08-25 8:19 ` Amir Goldstein
2020-08-25 10:07 ` Matthew Bobrowski
2020-08-25 11:45 ` Michael Kerrisk (man-pages)
2020-08-25 12:07 ` Amir Goldstein
2020-08-24 8:03 ` [PATCH 2/3] fanotify.7, fanotify_init.2: Document FAN_REPORT_DIR_FID Amir Goldstein
2020-08-24 9:53 ` Jan Kara
2020-08-24 23:24 ` Matthew Bobrowski
2020-08-24 8:03 ` [PATCH 3/3] fanotify.7, fanotify_init.2: Document FAN_REPORT_NAME Amir Goldstein
2020-08-24 10:00 ` Jan Kara
2020-08-24 23:28 ` Matthew Bobrowski
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=20200824235048.GA29428@mail.bobrowski.net \
--to=mbobrowski@mbobrowski.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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).