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 v1 1/2] fa_notify_mark(2): Support for FA_ flags has been backported to LTS kernels
Date: Fri, 12 Jul 2024 13:56:48 -0400 [thread overview]
Message-ID: <20240712175649.33057-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
man/man2/fanotify_mark.2 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/man/man2/fanotify_mark.2 b/man/man2/fanotify_mark.2
index f3fce0c4e4c4..edeadc883029 100644
--- a/man/man2/fanotify_mark.2
+++ b/man/man2/fanotify_mark.2
@@ -176,7 +176,7 @@ the update fails with
.B EEXIST
error.
.TP
-.BR FAN_MARK_IGNORE " (since Linux 6.0)"
+.BR FAN_MARK_IGNORE " (since Linux 6.0, 5.15.154, and 5.10.220)"
.\" commit e252f2ed1c8c6c3884ab5dd34e003ed21f1fe6e0
This flag has a similar effect as setting the
.B FAN_MARK_IGNORED_MASK
@@ -271,7 +271,7 @@ error.
This is a synonym for
.RB ( FAN_MARK_IGNORE | FAN_MARK_IGNORED_SURV_MODIFY ).
.TP
-.BR FAN_MARK_EVICTABLE " (since Linux 5.19)"
+.BR FAN_MARK_EVICTABLE " (since Linux 5.19, 5.15.154, and 5.10.220)"
.\" commit 5f9d3bd520261fd7a850818c71809fd580e0f30c
When an inode mark is created with this flag,
the inode object will not be pinned to the inode cache,
@@ -362,7 +362,7 @@ Create an event when a marked file or directory itself is deleted.
An fanotify group that identifies filesystem objects by file handles
is required.
.TP
-.BR FAN_FS_ERROR " (since Linux 5.16)"
+.BR FAN_FS_ERROR " (since Linux 5.16, 5.15.154, and 5.10.220)"
.\" commit 9709bd548f11a092d124698118013f66e1740f9b
Create an event when a filesystem error
leading to inconsistent filesystem metadata is detected.
@@ -399,7 +399,7 @@ directory.
An fanotify group that identifies filesystem objects by file handles
is required.
.TP
-.BR FAN_RENAME " (since Linux 5.17)"
+.BR FAN_RENAME " (since Linux 5.17, 5.15.154, and 5.10.220)"
.\" commit 8cc3b1ccd930fe6971e1527f0c4f1bdc8cb56026
This event contains the same information provided by events
.B FAN_MOVED_FROM
--
2.45.1
next reply other threads:[~2024-07-12 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 17:56 cel [this message]
2024-07-12 17:56 ` [PATCH v1 2/2] fa_notify_init(2): Support for FA_ flags has been backported to LTS kernels cel
2024-07-13 18:02 ` Amir Goldstein
2024-07-13 17:53 ` [PATCH v1 1/2] fa_notify_mark(2): " Amir Goldstein
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=20240712175649.33057-1-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;
as well as URLs for NNTP newsgroup(s).