From: Amir Goldstein <amir73il@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
linux-man@vger.kernel.org
Subject: [PATCH v2 3/4] fanotify_mark.2: Update w.r.t tmpfs support
Date: Sat, 20 Nov 2021 19:12:52 +0200 [thread overview]
Message-ID: <20211120171253.1385863-4-amir73il@gmail.com> (raw)
In-Reply-To: <20211120171253.1385863-1-amir73il@gmail.com>
tmpfs can be watched with FAN_REPORT_FID since kernel v5.13.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
man2/fanotify_mark.2 | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2
index cb69ac592..92309e684 100644
--- a/man2/fanotify_mark.2
+++ b/man2/fanotify_mark.2
@@ -414,7 +414,12 @@ The filesystem object indicated by
is not associated with a filesystem that supports
.I fsid
(e.g.,
-.BR tmpfs (5)).
+.BR fuse (4)).
+.BR tmpfs (5)
+did not support
+.I fsid
+prior to Linux 5.13.
+.\" commit 59cda49ecf6c9a32fae4942420701b6e087204f6
This error can be returned only with an fanotify group that identifies
filesystem objects by file handles.
.TP
--
2.33.1
next prev parent reply other threads:[~2021-11-20 17:13 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 ` Amir Goldstein [this message]
2021-11-20 17:12 ` [PATCH v2 4/4] fanotify_init.2: Document kernel commits Amir Goldstein
2021-11-22 16:56 ` [PATCH v2 0/4] fanotify man page updates for v5.13 Alejandro Colomar (man-pages)
2021-12-10 9:37 ` 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=20211120171253.1385863-4-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=alx.manpages@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