memorylost731/linux_man_pages_library · Datasets at Hugging Face

text stringlengths 0 234
about the underlying filesystem object correlated to an event.
an additional record of type
.br fan_event_info_type_fid
encapsulates the information about the object and is included alongside the
generic event metadata structure.
the file descriptor that is used to represent the object correlated to an
event is instead substituted with a file handle.
it is intended for applications that may find the use of a file handle to
identify an object more suitable than a file descriptor.
additionally, it may be used for applications monitoring a directory or a
filesystem that are interested in the directory entry modification events
.br fan_create ,
.br fan_delete ,
and
.br fan_move ,
or in events such as
.br fan_attrib ,
.br fan_delete_self ,
and
.br fan_move_self .
all the events above require an fanotify group that identifies filesystem
objects by file handles.
note that for the directory entry modification events the reported file handle
identifies the modified directory and not the created/deleted/moved child
object.
the use of
.br fan_class_content
or
.br fan_class_pre_content
is not permitted with this flag and will result in the error
.br einval .
see
.br fanotify (7)
for additional details.
.tp
.br fan_report_dir_fid " (since linux 5.9)"
events for fanotify groups initialized with this flag will contain
(see exceptions below) additional information about a directory object
correlated to an event.
an additional record of type
.br fan_event_info_type_dfid
encapsulates the information about the directory object and is included
alongside the generic event metadata structure.
for events that occur on a non-directory object, the additional structure
includes a file handle that identifies the parent directory filesystem object.
note that there is no guarantee that the directory filesystem object will be
found at the location described by the file handle information at the time
the event is received.
when combined with the flag
.br fan_report_fid ,
two records may be reported with events that occur on a non-directory object,
one to identify the non-directory object itself and one to identify the parent
directory object.
note that in some cases, a filesystem object does not have a parent,
for example, when an event occurs on an unlinked but open file.
in that case, with the
.br fan_report_fid
flag, the event will be reported with only one record to identify the
non-directory object itself, because there is no directory associated with
the event.
without the
.br fan_report_fid
flag, no event will be reported.
see
.br fanotify (7)
for additional details.
.tp
.br fan_report_name " (since linux 5.9)"
events for fanotify groups initialized with this flag will contain additional
information about the name of the directory entry correlated to an event.
this flag must be provided in conjunction with the flag
.br fan_report_dir_fid .
providing this flag value without
.br fan_report_dir_fid
will result in the error
.br einval .
this flag may be combined with the flag
.br fan_report_fid .
an additional record of type
.br fan_event_info_type_dfid_name ,
which encapsulates the information about the directory entry, is included
alongside the generic event metadata structure and substitutes the additional
information record of type
.br fan_event_info_type_dfid .
the additional record includes a file handle that identifies a directory
filesystem object followed by a name that identifies an entry in that
directory.
for the directory entry modification events
.br fan_create ,
.br fan_delete ,
and
.br fan_move ,
the reported name is that of the created/deleted/moved directory entry.
for other events that occur on a directory object, the reported file handle
is that of the directory object itself and the reported name is '.'.
for other events that occur on a non-directory object, the reported file handle
is that of the parent directory object and the reported name is the name of a
directory entry where the object was located at the time of the event.
the rationale behind this logic is that the reported directory file handle can
be passed to

about the underlying filesystem object correlated to an event.

an additional record of type

.br fan_event_info_type_fid

encapsulates the information about the object and is included alongside the

generic event metadata structure.

the file descriptor that is used to represent the object correlated to an

event is instead substituted with a file handle.

it is intended for applications that may find the use of a file handle to

identify an object more suitable than a file descriptor.

additionally, it may be used for applications monitoring a directory or a

filesystem that are interested in the directory entry modification events

.br fan_create ,

.br fan_delete ,

and

.br fan_move ,

or in events such as

.br fan_attrib ,

.br fan_delete_self ,

and

.br fan_move_self .

all the events above require an fanotify group that identifies filesystem

objects by file handles.

note that for the directory entry modification events the reported file handle

identifies the modified directory and not the created/deleted/moved child

object.

the use of

.br fan_class_content

or

.br fan_class_pre_content

is not permitted with this flag and will result in the error

.br einval .

see

.br fanotify (7)

for additional details.

.tp

.br fan_report_dir_fid " (since linux 5.9)"

events for fanotify groups initialized with this flag will contain

(see exceptions below) additional information about a directory object

correlated to an event.

an additional record of type

.br fan_event_info_type_dfid

encapsulates the information about the directory object and is included

alongside the generic event metadata structure.

for events that occur on a non-directory object, the additional structure

includes a file handle that identifies the parent directory filesystem object.

note that there is no guarantee that the directory filesystem object will be

found at the location described by the file handle information at the time

the event is received.

when combined with the flag

.br fan_report_fid ,

two records may be reported with events that occur on a non-directory object,

one to identify the non-directory object itself and one to identify the parent

directory object.

note that in some cases, a filesystem object does not have a parent,

for example, when an event occurs on an unlinked but open file.

in that case, with the

.br fan_report_fid

flag, the event will be reported with only one record to identify the

non-directory object itself, because there is no directory associated with

the event.

without the

.br fan_report_fid

flag, no event will be reported.

see

.br fanotify (7)

for additional details.

.tp

.br fan_report_name " (since linux 5.9)"

events for fanotify groups initialized with this flag will contain additional

information about the name of the directory entry correlated to an event.

this flag must be provided in conjunction with the flag

.br fan_report_dir_fid .

providing this flag value without

.br fan_report_dir_fid

will result in the error

.br einval .

this flag may be combined with the flag

.br fan_report_fid .

an additional record of type

.br fan_event_info_type_dfid_name ,

which encapsulates the information about the directory entry, is included

alongside the generic event metadata structure and substitutes the additional

information record of type

.br fan_event_info_type_dfid .

the additional record includes a file handle that identifies a directory

filesystem object followed by a name that identifies an entry in that

directory.

for the directory entry modification events

.br fan_create ,

.br fan_delete ,

and

.br fan_move ,

the reported name is that of the created/deleted/moved directory entry.

for other events that occur on a directory object, the reported file handle

is that of the directory object itself and the reported name is '.'.

for other events that occur on a non-directory object, the reported file handle

is that of the parent directory object and the reported name is the name of a

directory entry where the object was located at the time of the event.

the rationale behind this logic is that the reported directory file handle can

be passed to