2020-01-21 19:07:34 +00:00
|
|
|
.\" Copyright (C) 2013, Heinrich Schuchardt <xypron.glpk@gmx.de>
|
2014-04-25 05:56:02 +00:00
|
|
|
.\"
|
|
|
|
.\" %%%LICENSE_START(VERBATIM)
|
|
|
|
.\" Permission is granted to make and distribute verbatim copies of this
|
|
|
|
.\" manual provided the copyright notice and this permission notice are
|
|
|
|
.\" preserved on all copies.
|
|
|
|
.\"
|
|
|
|
.\" Permission is granted to copy and distribute modified versions of
|
|
|
|
.\" this manual under the conditions for verbatim copying, provided that
|
|
|
|
.\" the entire resulting derived work is distributed under the terms of
|
|
|
|
.\" a permission notice identical to this one.
|
|
|
|
.\"
|
|
|
|
.\" Since the Linux kernel and libraries are constantly changing, this
|
|
|
|
.\" manual page may be incorrect or out-of-date. The author(s) assume.
|
|
|
|
.\" no responsibility for errors or omissions, or for damages resulting.
|
|
|
|
.\" from the use of the information contained herein. The author(s) may.
|
|
|
|
.\" not have taken the same level of care in the production of this.
|
|
|
|
.\" manual, which is licensed free of charge, as they might when working.
|
|
|
|
.\" professionally.
|
|
|
|
.\"
|
|
|
|
.\" Formatted or processed versions of this manual, if unaccompanied by
|
|
|
|
.\" the source, must acknowledge the copyright and authors of this work.
|
|
|
|
.\" %%%LICENSE_END
|
iconv.1, locale.1, memusage.1, memusagestat.1, pldd.1, sprof.1, _syscall.2, add_key.2, adjtimex.2, bind.2, bpf.2, chown.2, clone.2, close.2, copy_file_range.2, eventfd.2, fanotify_init.2, fanotify_mark.2, fork.2, fsync.2, futex.2, getdents.2, getrlimit.2, getxattr.2, io_cancel.2, io_destroy.2, io_getevents.2, io_setup.2, ioctl_fat.2, ioctl_getfsmap.2, ioctl_ns.2, ioctl_tty.2, ioctl_userfaultfd.2, kcmp.2, keyctl.2, listen.2, listxattr.2, mbind.2, membarrier.2, memfd_create.2, mkdir.2, move_pages.2, mremap.2, msync.2, nfsservctl.2, open.2, perf_event_open.2, pidfd_send_signal.2, pipe.2, pivot_root.2, pkey_alloc.2, process_vm_readv.2, ptrace.2, readlink.2, readv.2, recv.2, recvmmsg.2, rename.2, request_key.2, s390_runtime_instr.2, sched_setaffinity.2, seccomp.2, send.2, sendmmsg.2, sigaltstack.2, signalfd.2, socket.2, socketpair.2, splice.2, spu_create.2, spu_run.2, statfs.2, syscall.2, sysctl.2, sysfs.2, tee.2, timer_getoverrun.2, timer_settime.2, umount.2, userfaultfd.2, utimensat.2, wait4.2, INFINITY.3, __ppc_get_timebase.3, __setfpucw.3, abort.3, aio_cancel.3, aio_error.3, aio_read.3, aio_return.3, atexit.3, backtrace.3, basename.3, bsearch.3, bswap.3, cacos.3, cacosh.3, catan.3, catanh.3, cexp2.3, clock_getcpuclockid.3, clog2.3, cmsg.3, confstr.3, div.3, dl_iterate_phdr.3, dlerror.3, dlinfo.3, dlopen.3, dlsym.3, duplocale.3, encrypt.3, end.3, endian.3, envz_add.3, err.3, expm1.3, fdim.3, flockfile.3, fmtmsg.3, frexp.3, ftw.3, get_nprocs_conf.3, get_phys_pages.3, getaddrinfo_a.3, getauxval.3, getdate.3, getdtablesize.3, getgrent_r.3, getgrouplist.3, gethostbyname.3, getline.3, getnameinfo.3, getopt.3, getprotoent_r.3, getpwent_r.3, getpwnam.3, getservent_r.3, getsubopt.3, getutent.3, glob.3, gnu_get_libc_version.3, hsearch.3, if_nameindex.3, inet.3, inet_net_pton.3, inet_ntop.3, inet_pton.3, insque.3, killpg.3, makecontext.3, mallinfo.3, malloc.3, malloc_hook.3, malloc_info.3, mallopt.3, matherr.3, mbsnrtowcs.3, mbstowcs.3, mcheck.3, mempcpy.3, mq_getattr.3, mq_notify.3, mtrace.3, newlocale.3, nextafter.3, ntp_gettime.3, offsetof.3, open_memstream.3, pow.3, printf.3, pthread_attr_init.3, pthread_attr_setdetachstate.3, pthread_attr_setguardsize.3, pthread_attr_setinheritsched.3, pthread_attr_setschedparam.3, pthread_attr_setschedpolicy.3, pthread_attr_setstack.3, pthread_attr_setstacksize.3, pthread_cancel.3, pthread_cleanup_push.3, pthread_create.3, pthread_detach.3, pthread_getattr_default_np.3, pthread_getattr_np.3, pthread_getcpuclockid.3, pthread_join.3, pthread_mutex_consistent.3, pthread_mutexattr_setrobust.3, pthread_setaffinity_np.3, pthread_setcancelstate.3, pthread_setname_np.3, pthread_setschedparam.3, pthread_sigmask.3, pthread_spin_init.3, pthread_testcancel.3, pthread_tryjoin_np.3, ptsname.3, qsort.3, rand.3, random.3, remainder.3, rpmatch.3, rtime.3, rtnetlink.3, scalb.3, scalbln.3, scandir.3, sem_getvalue.3, sem_wait.3, setaliasent.3, setlogmask.3, sigwait.3, sincos.3, sockatmark.3, stdarg.3, stpcpy.3, strcat.3, strfmon.3, strptime.3, strtod.3, strtok.3, strtol.3, strtoul.3, strverscmp.3, tsearch.3, uselocale.3, wcstok.3, wcstombs.3, wordexp.3, y0.3, loop.4, vcs.4, veth.4, charmap.5, core.5, filesystems.5, gai.conf.5, hosts.5, hosts.equiv.5, locale.5, nss.5, repertoiremap.5, securetty.5, shells.5, ttytype.5, ascii.7, complex.7, cpuset.7, credentials.7, fanotify.7, hier.7, inotify.7, ip.7, mount_namespaces.7, mq_overview.7, netlink.7, network_namespaces.7, pid_namespaces.7, pkeys.7, rtld-audit.7, rtnetlink.7, sem_overview.7, signal-safety.7, sock_diag.7, spufs.7, standards.7, symlink.7, tcp.7, time_namespaces.7, unix.7, user_namespaces.7, xattr.7, ldconfig.8: tstamp
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2020-06-09 12:43:54 +00:00
|
|
|
.TH FANOTIFY_INIT 2 2020-06-09 "Linux" "Linux Programmer's Manual"
|
2014-04-25 05:56:02 +00:00
|
|
|
.SH NAME
|
|
|
|
fanotify_init \- create and initialize fanotify group
|
|
|
|
.SH SYNOPSIS
|
|
|
|
.B #include <fcntl.h>
|
|
|
|
.br
|
|
|
|
.B #include <sys/fanotify.h>
|
2017-08-15 14:42:13 +00:00
|
|
|
.PP
|
2014-04-25 05:56:02 +00:00
|
|
|
.BI "int fanotify_init(unsigned int " flags ", unsigned int " event_f_flags );
|
|
|
|
.SH DESCRIPTION
|
|
|
|
For an overview of the fanotify API, see
|
|
|
|
.BR fanotify (7).
|
|
|
|
.PP
|
|
|
|
.BR fanotify_init ()
|
|
|
|
initializes a new fanotify group and returns a file descriptor for the event
|
|
|
|
queue associated with the group.
|
|
|
|
.PP
|
|
|
|
The file descriptor is used in calls to
|
|
|
|
.BR fanotify_mark (2)
|
2019-06-06 09:48:02 +00:00
|
|
|
to specify the files, directories, mounts or filesystems for which fanotify
|
|
|
|
events shall be created.
|
2014-04-25 05:56:02 +00:00
|
|
|
These events are received by reading from the file descriptor.
|
|
|
|
Some events are only informative, indicating that a file has been accessed.
|
2014-04-25 10:01:06 +00:00
|
|
|
Other events can be used to determine whether
|
|
|
|
another application is permitted to access a file or directory.
|
2014-04-25 05:56:02 +00:00
|
|
|
Permission to access filesystem objects is granted by writing to the file
|
|
|
|
descriptor.
|
|
|
|
.PP
|
|
|
|
Multiple programs may be using the fanotify interface at the same time to
|
|
|
|
monitor the same files.
|
|
|
|
.PP
|
|
|
|
In the current implementation, the number of fanotify groups per user is
|
|
|
|
limited to 128.
|
|
|
|
This limit cannot be overridden.
|
|
|
|
.PP
|
|
|
|
Calling
|
|
|
|
.BR fanotify_init ()
|
|
|
|
requires the
|
|
|
|
.B CAP_SYS_ADMIN
|
|
|
|
capability.
|
|
|
|
This constraint might be relaxed in future versions of the API.
|
2014-04-25 10:02:32 +00:00
|
|
|
Therefore, certain additional capability checks have been implemented as
|
2014-04-25 05:56:02 +00:00
|
|
|
indicated below.
|
|
|
|
.PP
|
|
|
|
The
|
|
|
|
.I flags
|
|
|
|
argument contains a multi-bit field defining the notification class of the
|
2014-05-05 09:45:37 +00:00
|
|
|
listening application and further single bit fields specifying the behavior
|
|
|
|
of the file descriptor.
|
2014-04-25 05:56:02 +00:00
|
|
|
.PP
|
2014-05-05 09:45:37 +00:00
|
|
|
If multiple listeners for permission events exist,
|
|
|
|
the notification class is used to establish the sequence
|
|
|
|
in which the listeners receive the events.
|
2014-04-25 05:56:02 +00:00
|
|
|
.PP
|
2014-04-25 10:03:11 +00:00
|
|
|
Only one of the following notification classes may be specified in
|
|
|
|
.IR flags :
|
2014-04-25 05:56:02 +00:00
|
|
|
.TP
|
|
|
|
.B FAN_CLASS_PRE_CONTENT
|
|
|
|
This value allows the receipt of events notifying that a file has been
|
|
|
|
accessed and events for permission decisions if a file may be accessed.
|
|
|
|
It is intended for event listeners that need to access files before they
|
|
|
|
contain their final data.
|
2014-05-05 09:45:37 +00:00
|
|
|
This notification class might be used by hierarchical storage managers,
|
|
|
|
for example.
|
2014-04-25 05:56:02 +00:00
|
|
|
.TP
|
|
|
|
.B FAN_CLASS_CONTENT
|
|
|
|
This value allows the receipt of events notifying that a file has been
|
|
|
|
accessed and events for permission decisions if a file may be accessed.
|
2014-05-05 09:45:37 +00:00
|
|
|
It is intended for event listeners that need to access files when they
|
|
|
|
already contain their final content.
|
2014-04-25 05:56:02 +00:00
|
|
|
This notification class might be used by malware detection programs, for
|
|
|
|
example.
|
|
|
|
.TP
|
|
|
|
.B FAN_CLASS_NOTIF
|
|
|
|
This is the default value.
|
|
|
|
It does not need to be specified.
|
|
|
|
This value only allows the receipt of events notifying that a file has been
|
|
|
|
accessed.
|
|
|
|
Permission decisions before the file is accessed are not possible.
|
|
|
|
.PP
|
|
|
|
Listeners with different notification classes will receive events in the
|
2014-04-25 10:04:49 +00:00
|
|
|
order
|
2014-04-25 05:56:02 +00:00
|
|
|
.BR FAN_CLASS_PRE_CONTENT ,
|
|
|
|
.BR FAN_CLASS_CONTENT ,
|
|
|
|
.BR FAN_CLASS_NOTIF .
|
2014-05-07 06:55:36 +00:00
|
|
|
The order of notification for listeners in the same notification class
|
|
|
|
is undefined.
|
2014-04-25 05:56:02 +00:00
|
|
|
.PP
|
2014-05-07 06:55:36 +00:00
|
|
|
The following bits can additionally be set in
|
2014-04-25 05:56:02 +00:00
|
|
|
.IR flags :
|
|
|
|
.TP
|
|
|
|
.B FAN_CLOEXEC
|
2014-05-07 06:55:36 +00:00
|
|
|
Set the close-on-exec flag
|
2014-04-25 05:56:02 +00:00
|
|
|
.RB ( FD_CLOEXEC )
|
|
|
|
on the new file descriptor.
|
|
|
|
See the description of the
|
|
|
|
.B O_CLOEXEC
|
|
|
|
flag in
|
|
|
|
.BR open (2).
|
|
|
|
.TP
|
|
|
|
.B FAN_NONBLOCK
|
2014-05-07 06:55:36 +00:00
|
|
|
Enable the nonblocking flag
|
2014-04-25 05:56:02 +00:00
|
|
|
.RB ( O_NONBLOCK )
|
|
|
|
for the file descriptor.
|
|
|
|
Reading from the file descriptor will not block.
|
2014-04-25 10:05:48 +00:00
|
|
|
Instead, if no data is available,
|
2014-04-25 05:56:02 +00:00
|
|
|
.BR read (2)
|
capget.2, fanotify_init.2, fcntl.2, ioctl_tty.2, madvise.2, mbind.2, prctl.2, sched_setaffinity.2, hash.3, isgreater.3, posix_fallocate.3, sigvec.3, full.4, sd.4, wavelan.4, core.5, host.conf.5, epoll.7, signal.7, unix.7, user_namespaces.7: wfix (will fail --> fail/fails)
Reported-by: Pedro Alves <palves@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2017-10-20 10:36:42 +00:00
|
|
|
fails with the error
|
2014-04-25 10:05:48 +00:00
|
|
|
.BR EAGAIN .
|
2014-04-25 05:56:02 +00:00
|
|
|
.TP
|
|
|
|
.B FAN_UNLIMITED_QUEUE
|
2014-05-07 06:55:36 +00:00
|
|
|
Remove the limit of 16384 events for the event queue.
|
|
|
|
Use of this flag requires the
|
2014-04-25 05:56:02 +00:00
|
|
|
.B CAP_SYS_ADMIN
|
|
|
|
capability.
|
|
|
|
.TP
|
|
|
|
.B FAN_UNLIMITED_MARKS
|
2014-05-07 06:55:36 +00:00
|
|
|
Remove the limit of 8192 marks.
|
|
|
|
Use of this flag requires the
|
2014-04-25 05:56:02 +00:00
|
|
|
.B CAP_SYS_ADMIN
|
|
|
|
capability.
|
2018-11-17 16:32:10 +00:00
|
|
|
.TP
|
|
|
|
.BR FAN_REPORT_TID " (since Linux 4.20)"
|
|
|
|
.\" commit d0a6a87e40da49cfc7954c491d3065a25a641b29
|
2019-02-26 16:25:36 +00:00
|
|
|
Report thread ID (TID) instead of process ID (PID)
|
|
|
|
in the
|
|
|
|
.I pid
|
|
|
|
field of the
|
|
|
|
.I "struct fanotify_event_metadata"
|
|
|
|
supplied to
|
|
|
|
.BR read (2)
|
|
|
|
(see
|
|
|
|
.BR fanotify (7)).
|
2020-05-29 09:25:29 +00:00
|
|
|
.TP
|
|
|
|
.BR FAN_REPORT_FID " (since Linux 5.1)"
|
|
|
|
.\" commit a8b13aa20afb69161b5123b4f1acc7ea0a03d360
|
|
|
|
This value allows the receipt of events which contain additional information
|
|
|
|
about the underlying filesystem object correlated to an event.
|
|
|
|
An additional structure 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 that are interested in
|
|
|
|
directory entry events, such as
|
|
|
|
.BR FAN_CREATE ,
|
|
|
|
.BR FAN_ATTRIB ,
|
|
|
|
.BR FAN_MOVE ,
|
|
|
|
and
|
|
|
|
.BR FAN_DELETE
|
|
|
|
for example.
|
|
|
|
Note that the use of directory modification events are not supported when
|
|
|
|
monitoring a mount point.
|
|
|
|
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 information.
|
2014-04-25 05:56:02 +00:00
|
|
|
.PP
|
2014-05-07 06:55:36 +00:00
|
|
|
The
|
2014-04-25 05:56:02 +00:00
|
|
|
.I event_f_flags
|
2014-05-07 06:55:36 +00:00
|
|
|
argument
|
|
|
|
defines the file status flags that will be set on the open file descriptions
|
|
|
|
that are created for fanotify events.
|
|
|
|
For details of these flags, see the description of the
|
2014-04-25 05:56:02 +00:00
|
|
|
.I flags
|
2014-05-07 06:55:36 +00:00
|
|
|
values in
|
|
|
|
.BR open (2).
|
2014-05-15 17:35:44 +00:00
|
|
|
.I event_f_flags
|
2014-05-18 07:46:30 +00:00
|
|
|
includes a multi-bit field for the access mode.
|
2014-05-15 17:35:44 +00:00
|
|
|
This field can take the following values:
|
2014-04-25 05:56:02 +00:00
|
|
|
.TP
|
|
|
|
.B O_RDONLY
|
|
|
|
This value allows only read access.
|
|
|
|
.TP
|
|
|
|
.B O_WRONLY
|
|
|
|
This value allows only write access.
|
|
|
|
.TP
|
|
|
|
.B O_RDWR
|
|
|
|
This value allows read and write access.
|
2014-05-15 17:35:44 +00:00
|
|
|
.PP
|
|
|
|
Additional bits can be set in
|
|
|
|
.IR event_f_flags .
|
|
|
|
The most useful values are:
|
2014-04-25 05:56:02 +00:00
|
|
|
.TP
|
|
|
|
.B O_LARGEFILE
|
add_key.2, alloc_hugepages.2, execve.2, fanotify_init.2, getrlimit.2, listxattr.2, mmap.2, shmget.2, malloc.3, random.4, st.4, bootparam.7, epoll.7, keyrings.7, pipe.7, xattr.7: Use non-breaking space for measurement units
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2017-08-18 10:28:20 +00:00
|
|
|
Enable support for files exceeding 2\ GB.
|
2014-04-25 05:56:02 +00:00
|
|
|
Failing to set this flag will result in an
|
|
|
|
.B EOVERFLOW
|
2014-05-05 09:45:37 +00:00
|
|
|
error when trying to open a large file which is monitored by
|
|
|
|
an fanotify group on a 32-bit system.
|
2014-05-15 17:35:44 +00:00
|
|
|
.TP
|
2016-02-06 15:50:35 +00:00
|
|
|
.BR O_CLOEXEC " (since Linux 3.18)"
|
|
|
|
.\" commit 0b37e097a648aa71d4db1ad108001e95b69a2da4
|
2014-05-15 17:35:44 +00:00
|
|
|
Enable the close-on-exec flag for the file descriptor.
|
2014-05-18 07:46:30 +00:00
|
|
|
See the description of the
|
|
|
|
.B O_CLOEXEC
|
|
|
|
flag in
|
|
|
|
.BR open (2)
|
|
|
|
for reasons why this may be useful.
|
2014-05-15 17:35:44 +00:00
|
|
|
.PP
|
|
|
|
The following are also allowable:
|
|
|
|
.BR O_APPEND ,
|
|
|
|
.BR O_DSYNC ,
|
|
|
|
.BR O_NOATIME ,
|
|
|
|
.BR O_NONBLOCK ,
|
|
|
|
and
|
|
|
|
.BR O_SYNC .
|
2014-05-18 07:46:30 +00:00
|
|
|
Specifying any other flag in
|
|
|
|
.I event_f_flags
|
|
|
|
yields the error
|
2014-05-15 17:35:44 +00:00
|
|
|
.B EINVAL
|
|
|
|
(but see BUGS).
|
2014-04-25 05:56:02 +00:00
|
|
|
.SH RETURN VALUE
|
|
|
|
On success,
|
|
|
|
.BR fanotify_init ()
|
|
|
|
returns a new file descriptor.
|
2014-04-25 10:11:08 +00:00
|
|
|
On error, \-1 is returned, and
|
2014-04-25 05:56:02 +00:00
|
|
|
.I errno
|
|
|
|
is set to indicate the error.
|
|
|
|
.SH ERRORS
|
|
|
|
.TP
|
|
|
|
.B EINVAL
|
|
|
|
An invalid value was passed in
|
2014-05-15 17:35:44 +00:00
|
|
|
.I flags
|
|
|
|
or
|
|
|
|
.IR event_f_flags .
|
2014-04-25 05:56:02 +00:00
|
|
|
.B FAN_ALL_INIT_FLAGS
|
2019-06-06 09:48:02 +00:00
|
|
|
(deprecated since Linux kernel version 4.20)
|
|
|
|
.\" commit 23c9deeb3285d34fd243abb3d6b9f07db60c3cf4
|
2014-05-15 17:35:44 +00:00
|
|
|
defines all allowable bits for
|
|
|
|
.IR flags .
|
2014-04-25 05:56:02 +00:00
|
|
|
.TP
|
|
|
|
.B EMFILE
|
2014-05-07 06:55:36 +00:00
|
|
|
The number of fanotify groups for this user exceeds 128.
|
2014-04-25 05:56:02 +00:00
|
|
|
.TP
|
2017-11-09 09:15:51 +00:00
|
|
|
.B EMFILE
|
2015-12-27 15:26:07 +00:00
|
|
|
The per-process limit on the number of open file descriptors has been reached.
|
|
|
|
.TP
|
2014-04-25 05:56:02 +00:00
|
|
|
.B ENOMEM
|
|
|
|
The allocation of memory for the notification group failed.
|
|
|
|
.TP
|
2014-05-01 05:47:11 +00:00
|
|
|
.B ENOSYS
|
|
|
|
This kernel does not implement
|
|
|
|
.BR fanotify_init ().
|
2014-05-07 06:55:36 +00:00
|
|
|
The fanotify API is available only if the kernel was configured with
|
|
|
|
.BR CONFIG_FANOTIFY .
|
2014-05-01 05:47:11 +00:00
|
|
|
.TP
|
2014-04-25 05:56:02 +00:00
|
|
|
.B EPERM
|
|
|
|
The operation is not permitted because the caller lacks the
|
|
|
|
.B CAP_SYS_ADMIN
|
|
|
|
capability.
|
|
|
|
.SH VERSIONS
|
|
|
|
.BR fanotify_init ()
|
|
|
|
was introduced in version 2.6.36 of the Linux kernel and enabled in version
|
|
|
|
2.6.37.
|
iconv.1, localedef.1, access.2, execveat.2, fanotify_init.2, futex.2, ioctl_fat.2, mount.2, ftw.3, sd.4, tty_ioctl.4, fanotify.7, futex.7, posixoptions.7, iconvconfig.8: srcfix: Remove useless quotes from .SS and .SH sections
Signed-off-by: Stéphane Aulery <saulery@free.fr>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2015-03-08 02:03:52 +00:00
|
|
|
.SH CONFORMING TO
|
2014-04-25 05:56:02 +00:00
|
|
|
This system call is Linux-specific.
|
2014-05-01 14:47:39 +00:00
|
|
|
.SH BUGS
|
2016-08-21 10:43:08 +00:00
|
|
|
The following bug was present in Linux kernels before version 3.18:
|
2014-09-29 14:25:53 +00:00
|
|
|
.IP * 3
|
2016-08-21 10:43:08 +00:00
|
|
|
.\" Fixed by commit 0b37e097a648aa71d4db1ad108001e95b69a2da4
|
2014-09-29 14:27:06 +00:00
|
|
|
The
|
2014-09-29 14:25:53 +00:00
|
|
|
.B O_CLOEXEC
|
2014-09-29 14:27:06 +00:00
|
|
|
is ignored when passed in
|
|
|
|
.IR event_f_flags .
|
2014-09-29 14:25:53 +00:00
|
|
|
.PP
|
2014-09-29 14:32:23 +00:00
|
|
|
The following bug was present in Linux kernels before version 3.14:
|
2014-05-01 14:47:39 +00:00
|
|
|
.IP * 3
|
2014-09-29 14:32:23 +00:00
|
|
|
.\" Fixed by commit 48149e9d3a7e924010a0daab30a6197b7d7b6580
|
2014-05-01 20:01:46 +00:00
|
|
|
The
|
2014-05-01 14:47:39 +00:00
|
|
|
.I event_f_flags
|
2014-05-01 20:13:35 +00:00
|
|
|
argument is not checked for invalid flags.
|
2014-05-01 20:01:46 +00:00
|
|
|
Flags that are intended only for internal use,
|
|
|
|
such as
|
2014-05-01 14:47:39 +00:00
|
|
|
.BR FMODE_EXEC ,
|
2014-05-01 20:01:46 +00:00
|
|
|
can be set, and will consequently be set for the file descriptors
|
|
|
|
returned when reading from the fanotify file descriptor.
|
iconv.1, localedef.1, access.2, execveat.2, fanotify_init.2, futex.2, ioctl_fat.2, mount.2, ftw.3, sd.4, tty_ioctl.4, fanotify.7, futex.7, posixoptions.7, iconvconfig.8: srcfix: Remove useless quotes from .SS and .SH sections
Signed-off-by: Stéphane Aulery <saulery@free.fr>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2015-03-08 02:03:52 +00:00
|
|
|
.SH SEE ALSO
|
2014-04-25 05:56:02 +00:00
|
|
|
.BR fanotify_mark (2),
|
|
|
|
.BR fanotify (7)
|