LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

fanotify.7: Adjust description of the fanotify queue 

Update as per http://www.spinics.net/lists/linux-man/msg05624.html
where Jan Kara proposed to clarify the deletion of events from the
fanotify queue and the occurrence of ENOENT when writing to the
fanotify file descriptor.

Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Heinrich Schuchardt 2014-05-06 20:41:06 +02:00 committed by Michael Kerrisk
parent b4112efb58
commit a662500625
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
man7/fanotify.7
View File

@ -113,10 +113,11 @@ whether permission for a file access shall be granted.
For these events, the recipient must write a response which decides whether
access is granted or not.
Queue entries for notification events are removed when the event has been
An event is removed from the event queue of the fanotify group when it has been
read.
Queue entries for permission events are removed when the permission
decision has been taken by writing to the fanotify file descriptor.
Permission events that have been read are kept in an internal list of the
fanotify group until either a permission decision has been taken by writing to
the fanotify file descriptor or the fanotify file descriptor is closed.
.SS Reading fanotify events
Calling
.BR read (2)
@ -400,8 +401,8 @@ in the response structure is not valid.
The file descriptor
.I fd
in the response structure is not valid.
This might occur because the file was already deleted by another thread or
process.
This may occur when a response for the permission event already has been
written before.
.SH VERSIONS
The fanotify API was introduced in version 2.6.36 of the Linux kernel and
enabled in version 2.6.37.