summaryrefslogtreecommitdiffstats
path: root/man2/fanotify_mark.2
diff options
context:
space:
mode:
Diffstat (limited to 'man2/fanotify_mark.2')
-rw-r--r--man2/fanotify_mark.246
1 files changed, 23 insertions, 23 deletions
diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2
index f3fce0c4e..044e9bd89 100644
--- a/man2/fanotify_mark.2
+++ b/man2/fanotify_mark.2
@@ -18,7 +18,7 @@ Standard C library
.fi
.SH DESCRIPTION
For an overview of the fanotify API, see
-.BR fanotify (7).
+.MR fanotify 7 .
.P
.BR fanotify_mark ()
adds, removes, or modifies an fanotify mark on a filesystem object.
@@ -28,7 +28,7 @@ is to be marked.
The
.I fanotify_fd
argument is a file descriptor returned by
-.BR fanotify_init (2).
+.MR fanotify_init 2 .
.P
.I flags
is a bit mask describing the modification to perform.
@@ -382,7 +382,7 @@ filesystem reports
events.
.IP
See
-.BR fanotify (7)
+.MR fanotify 7
for additional details.
.TP
.BR FAN_MOVED_FROM " (since Linux 5.1)"
@@ -447,10 +447,10 @@ is required.
.TP
.B FAN_ONDIR
Create events for directories\[em]for example, when
-.BR opendir (3),
-.BR readdir (3)
+.MR opendir 3 ,
+.MR readdir 3
(but see BUGS), and
-.BR closedir (3)
+.MR closedir 3
are called.
Without this flag, events are created only for files.
In the context of directory entry events, such as
@@ -463,8 +463,8 @@ specifying the flag
.B FAN_ONDIR
is required in order to create events when subdirectory entries are
modified (i.e.,
-.BR mkdir (2)/
-.BR rmdir (2)).
+.MR mkdir 2 /
+.MR rmdir 2 ).
.TP
.B FAN_EVENT_ON_CHILD
Events for the immediate children of marked directories shall be created.
@@ -543,7 +543,7 @@ then the filesystem object to be marked is determined by interpreting
.I pathname
relative to the current working directory.
(See
-.BR openat (2)
+.MR openat 2
for an explanation of why the
.I dirfd
argument is useful.)
@@ -662,8 +662,8 @@ and
is not associated with a filesystem that supports
.I fsid
(e.g.,
-.BR fuse (4)).
-.BR tmpfs (5)
+.MR fuse 4 ).
+.MR tmpfs 5
did not support
.I fsid
prior to Linux 5.13.
@@ -687,9 +687,9 @@ The necessary memory could not be allocated.
The number of marks for this user exceeds the limit and the
.B FAN_UNLIMITED_MARKS
flag was not specified when the fanotify file descriptor was created with
-.BR fanotify_init (2).
+.MR fanotify_init 2 .
See
-.BR fanotify (7)
+.MR fanotify 7
for details about this limit.
.TP
.B ENOSYS
@@ -748,7 +748,7 @@ that does not support the encoding of file handles.
This error can be returned only with an fanotify group that identifies
filesystem objects by file handles.
Calling
-.BR name_to_handle_at (2)
+.MR name_to_handle_at 2
with the flag
.BR AT_HANDLE_FID " (since Linux 6.5)"
.\" commit 96b2b072ee62be8ae68c8ecf14854c4d0505a8f8
@@ -762,7 +762,7 @@ The operation is not permitted because the caller lacks a required capability.
The filesystem object indicated by
.I pathname
resides within a filesystem subvolume (e.g.,
-.BR btrfs (5))
+.MR btrfs 5 )
which uses a different
.I fsid
than its root superblock.
@@ -785,19 +785,19 @@ events of these types will be returned only when the direct execution of a
program occurs.
More specifically, this means that events of these types will be generated
for files that are opened using
-.BR execve (2),
-.BR execveat (2),
+.MR execve 2 ,
+.MR execveat 2 ,
or
-.BR uselib (2).
+.MR uselib 2 .
Events of these types will not be raised in the situation where an
interpreter is passed (or reads) a file for interpretation.
.P
Additionally, if a mark has also been placed on the Linux dynamic
linker, a user should also expect to receive an event for it when
an ELF object has been successfully opened using
-.BR execve (2)
+.MR execve 2
or
-.BR execveat (2).
+.MR execveat 2 .
.P
For example, if the following ELF binary were to be invoked and a
.B FAN_OPEN_EXEC
@@ -833,7 +833,7 @@ and
must specify a valid filesystem object, even though this object is not used.
.IP \[bu]
.\" Fixed by commit d4c7cf6cffb1bc711a833b5e304ba5bcfe76398b
-.BR readdir (2)
+.MR readdir 2
does not generate a
.B FAN_ACCESS
event.
@@ -846,5 +846,5 @@ is called with
.I flags
is not checked for invalid values.
.SH SEE ALSO
-.BR fanotify_init (2),
-.BR fanotify (7)
+.MR fanotify_init 2 ,
+.MR fanotify 7