From: cel@kernel.org
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
amir73il@gmail.com, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v2 2/3] fanotify_init(2): Support for FA_ flags has been backported to LTS kernels
Date: Sat, 13 Jul 2024 14:15:47 -0400 [thread overview]
Message-ID: <20240713181548.38002-3-cel@kernel.org> (raw)
In-Reply-To: <20240713181548.38002-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
man/man2/fanotify_init.2 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/man/man2/fanotify_init.2 b/man/man2/fanotify_init.2
index e5f9cbf298ee..12378ac05255 100644
--- a/man/man2/fanotify_init.2
+++ b/man/man2/fanotify_init.2
@@ -295,7 +295,7 @@ for additional details.
This is a synonym for
.RB ( FAN_REPORT_DIR_FID | FAN_REPORT_NAME ).
.TP
-.BR FAN_REPORT_TARGET_FID " (since Linux 5.17)"
+.BR FAN_REPORT_TARGET_FID " (since Linux 5.17, 5.15.154, and 5.10.220)"
.\" commit d61fd650e9d206a71fda789f02a1ced4b19944c4
Events for fanotify groups initialized with this flag
will contain additional information about the child
@@ -330,7 +330,7 @@ that the directory entry is referring to.
This is a synonym for
.RB ( FAN_REPORT_DFID_NAME | FAN_REPORT_FID | FAN_REPORT_TARGET_FID ).
.TP
-.BR FAN_REPORT_PIDFD " (since Linux 5.15)"
+.BR FAN_REPORT_PIDFD " (since Linux 5.15 and 5.10.220)"
.\" commit af579beb666aefb17e9a335c12c788c92932baf1
Events for fanotify groups initialized with this flag will contain
an additional information record alongside the generic
@@ -460,14 +460,14 @@ The fanotify API is available only if the kernel was configured with
.B EPERM
The operation is not permitted because the caller lacks a required capability.
.SH VERSIONS
-Prior to Linux 5.13,
+Prior to Linux 5.13 (and 5.10.220),
.\" commit 7cea2a3c505e87a9d6afc78be4a7f7be636a73a7
calling
.BR fanotify_init ()
required the
.B CAP_SYS_ADMIN
capability.
-Since Linux 5.13,
+Since Linux 5.13 (and 5.10.220),
.\" commit 7cea2a3c505e87a9d6afc78be4a7f7be636a73a7
users may call
.BR fanotify_init ()
--
2.45.1
next prev parent reply other threads:[~2024-07-13 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 18:15 [PATCH v2 0/3] Update fanotify man pages for NFSD filecache backports cel
2024-07-13 18:15 ` [PATCH v2 1/3] fanotify_mark(2): Support for FA_ flags has been backported to LTS kernels cel
2024-07-13 18:15 ` cel [this message]
2024-07-13 18:41 ` [PATCH v2 2/3] fanotify_init(2): " Amir Goldstein
2024-07-13 18:15 ` [PATCH v2 3/3] fanotify(7): Document changes " cel
2024-07-13 18:40 ` Amir Goldstein
2024-07-22 20:36 ` [PATCH v2 0/3] Update fanotify man pages for NFSD filecache backports Alejandro Colomar
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=20240713181548.38002-3-cel@kernel.org \
--to=cel@kernel.org \
--cc=alx@kernel.org \
--cc=amir73il@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.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