mirror of https://github.com/mkerrisk/man-pages
fanotify.7: Since Linux 3.19, fallocate(2) generates FAN_MODIFY events
Reported-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
f9bfa911aa
commit
707914e9bc
|
@ -485,6 +485,17 @@ Monitoring mounts offers the capability to monitor a whole directory tree.
|
|||
The event queue can overflow.
|
||||
In this case, events are lost.
|
||||
.SH BUGS
|
||||
Before Linux 3.19,
|
||||
.BR fallocate (2)
|
||||
did not generate fanotify events.
|
||||
Since Linux 3.19,
|
||||
.\" commit 820c12d5d6c0890bc93dd63893924a13041fdc35
|
||||
calls to
|
||||
.BR fallocate (2)
|
||||
generate
|
||||
.B FAN_MODIFY
|
||||
events.
|
||||
|
||||
As of Linux 3.17,
|
||||
the following bugs exist:
|
||||
.IP * 3
|
||||
|
@ -497,10 +508,6 @@ A listener that marked a mount will be notified only of events that were
|
|||
triggered for a filesystem object using the same mount.
|
||||
Any other event will pass unnoticed.
|
||||
.IP *
|
||||
Calling
|
||||
.BR fallocate (2)
|
||||
does not create any fanotify events.
|
||||
.IP *
|
||||
.\" FIXME . A patch was proposed.
|
||||
When an event is generated,
|
||||
no check is made to see whether the user ID of the
|
||||
|
|
Loading…
Reference in New Issue