Re: [PATCH 1/1] fanotify.7: adjust description of the fanotify queue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue 06-05-14 20:41:06, Heinrich Schuchardt wrote:
> In http://www.spinics.net/lists/linux-man/msg05624.html
> Jan Kara proposed to clarify the deletion of events from the fanotify queue
> and the occurence of ENOENT when writing to the fanotify file descriptor.
  This looks good. Thanks!

								Honza
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@xxxxxx>
> ---
>  man7/fanotify.7 | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/man7/fanotify.7 b/man7/fanotify.7
> index 182d2d7..bce70ac 100644
> --- a/man7/fanotify.7
> +++ b/man7/fanotify.7
> @@ -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.
> -- 
> 2.0.0.rc0
> 
-- 
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux