From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
linux-man@vger.kernel.org
Subject: Re: [PATCH v2 0/4] fanotify man page updates for v5.13
Date: Mon, 22 Nov 2021 17:56:59 +0100 [thread overview]
Message-ID: <4c1659ad-dbaf-dccd-95bb-fe224c4c0912@gmail.com> (raw)
In-Reply-To: <20211120171253.1385863-1-amir73il@gmail.com>
Hi Amir,
On 11/20/21 18:12, Amir Goldstein wrote:
> Hi Alejandro,
>
> This is a re-post of updates for v5.13 that I posted last March [1].
>
> Thanks,
> Amir.
>
> Changes since v1:
> - Update comment regarding tmpfs
> - Document kernel commits
>
> [1] https://lore.kernel.org/linux-man/20210318160817.3586288-1-amir73il@gmail.com/
>
> Amir Goldstein (3):
> fanotify_init.2, fanotify_mark.2, fanotify.7: Configurable limits
> fanotify_mark.2: Update w.r.t tmpfs support
> fanotify_init.2: Document kernel commits
>
> Matthew Bobrowski (1):
> fanotify_init.2, fanotify_mark.2: Document unprivileged listener
Patch set applied.
See some tweaks below.
Thanks!
Alex
---
fanotify_init.2: Minor tweaks to Matthew's patch
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Matthew Bobrowski <mbobrowski@mbobrowski.org>
Cc: Amir Goldstein <amir73il@gmail.com>
diff --git a/man2/fanotify_init.2 b/man2/fanotify_init.2
index 7a1c21037..e463372f3 100644
--- a/man2/fanotify_init.2
+++ b/man2/fanotify_init.2
@@ -426,23 +426,23 @@ The user cannot request for an unlimited number of
marks by using
.BR FAN_UNLIMITED_MARKS .
.IP * 3
The user cannot request to use either notification classes
-.BR FAN_CLASS_CONTENT
+.B FAN_CLASS_CONTENT
or
.BR FAN_CLASS_PRE_CONTENT .
This means that user cannot request permission events.
.IP * 3
The user is required to create a group that identifies filesystem
objects by
file handles, for example, by providing the
-.BR FAN_REPORT_FID
+.B FAN_REPORT_FID
flag.
.IP * 3
The user is limited to only mark inodes.
The ability to mark a mount or filesystem via
-.BR fanotify_mark()
+.BR fanotify_mark ()
through the use of
-.BR FAN_MARK_MOUNT
+.B FAN_MARK_MOUNT
or
-.BR FAN_MARK_FILESYSTEM
+.B FAN_MARK_FILESYSTEM
is not permitted.
.IP * 3
The event object in the event queue is limited in terms of the information
--
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-11-22 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 17:12 [PATCH v2 0/4] fanotify man page updates for v5.13 Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 1/4] fanotify_init.2, fanotify_mark.2: Document unprivileged listener Amir Goldstein
2021-11-20 17:19 ` Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 2/4] fanotify_init.2, fanotify_mark.2, fanotify.7: Configurable limits Amir Goldstein
2021-11-20 17:19 ` Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 3/4] fanotify_mark.2: Update w.r.t tmpfs support Amir Goldstein
2021-11-20 17:12 ` [PATCH v2 4/4] fanotify_init.2: Document kernel commits Amir Goldstein
2021-11-22 16:56 ` Alejandro Colomar (man-pages) [this message]
2021-12-10 9:37 ` [PATCH v2 0/4] fanotify man page updates for v5.13 Amir Goldstein
2021-12-10 13:56 ` Alejandro Colomar (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=4c1659ad-dbaf-dccd-95bb-fe224c4c0912@gmail.com \
--to=alx.manpages@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-man@vger.kernel.org \
--cc=mbobrowski@mbobrowski.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