[PATCH 0/3] inotify.7, fanotify.7: fallocate triggers no event

[PATCH 0/3] inotify.7, fanotify.7: fallocate triggers no event

[Heinrich Schuchardt]

the fanotify.7 and inotify.7 manpages do not describe whether fallocate.2 will
create events (FAN_MODIFY, IN_MODIFY).
Looking at fs/open.c no event seems to be created.
I ran a test program and could not detect any FAN_MODIFY event.

Heinrich Schuchardt (3):
  fanotify.7: bugs still not fixed in 3.17
  fanotify.7: fallocate creates no events
  inotify.7: fallocate does not trigger inotify events

 man7/fanotify.7 | 6 +++++-
 man7/inotify.7  | 4 ++++
 2 files changed, 9 insertions(+), 1 deletion(-)

-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 1/3] fanotify.7: bugs still not fixed in 3.17

[Heinrich Schuchardt]

I bumped the Linux version number in the BUGS section to 3.17.

Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
---
 man7/fanotify.7 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man7/fanotify.7 b/man7/fanotify.7
index b6456d5..bc5a11c 100644
--- a/man7/fanotify.7
+++ b/man7/fanotify.7
@@ -485,7 +485,7 @@ Monitoring mounts offers the capability to monitor a whole directory tree.
 The event queue can overflow.
 In this case, events are lost.
 .SH BUGS
-As of Linux 3.15,
+As of Linux 3.17,
 the following bugs exist:
 .IP * 3
 .\" FIXME . A patch was proposed.
-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 2/3] fanotify.7: fallocate creates no events

[Heinrich Schuchardt]

fallocate(2) should create FAN_MODIFY events but does not.

Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
---
 man7/fanotify.7 | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/man7/fanotify.7 b/man7/fanotify.7
index bc5a11c..e718249 100644
--- a/man7/fanotify.7
+++ b/man7/fanotify.7
@@ -488,6 +488,10 @@ In this case, events are lost.
 As of Linux 3.17,
 the following bugs exist:
 .IP * 3
+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
-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 3/3] inotify.7: fallocate does not trigger inotify events

[Heinrich Schuchardt]

Calling fallocate.2 does not result in inotify events.

Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
---
 man7/inotify.7 | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/man7/inotify.7 b/man7/inotify.7
index a0e2528..7f45ba9 100644
--- a/man7/inotify.7
+++ b/man7/inotify.7
@@ -752,6 +752,10 @@ and also the possibility that there may not be any
 .B IN_MOVED_TO
 event.
 .SH BUGS
+As of kernel 3.17, calling
+.BR fallocate (2) 
+does not create any inotify events.
+
 .\" FIXME . kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321
 .\" implies that unmount events were buggy 2.6.11 to 2.6.36
 .\"
-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 1/3] fanotify.7: bugs still not fixed in 3.17

[Michael Kerrisk (man-pages)]

Thanks, Heinrich.

Applied.

Cheers,

Michael

On 10/03/2014 12:05 AM, Heinrich Schuchardt wrote:
> I bumped the Linux version number in the BUGS section to 3.17.
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
>  man7/fanotify.7 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man7/fanotify.7 b/man7/fanotify.7
> index b6456d5..bc5a11c 100644
> --- a/man7/fanotify.7
> +++ b/man7/fanotify.7
> @@ -485,7 +485,7 @@ Monitoring mounts offers the capability to monitor a whole directory tree.
>  The event queue can overflow.
>  In this case, events are lost.
>  .SH BUGS
> -As of Linux 3.15,
> +As of Linux 3.17,
>  the following bugs exist:
>  .IP * 3
>  .\" FIXME . A patch was proposed.
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 2/3] fanotify.7: fallocate creates no events

[Michael Kerrisk (man-pages)]

Thanks, Heinrich.

Applied.

Cheers,

Michael

On 10/03/2014 12:06 AM, Heinrich Schuchardt wrote:
> fallocate(2) should create FAN_MODIFY events but does not.
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
>  man7/fanotify.7 | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/man7/fanotify.7 b/man7/fanotify.7
> index bc5a11c..e718249 100644
> --- a/man7/fanotify.7
> +++ b/man7/fanotify.7
> @@ -488,6 +488,10 @@ In this case, events are lost.
>  As of Linux 3.17,
>  the following bugs exist:
>  .IP * 3
> +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
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 3/3] inotify.7: fallocate does not trigger inotify events

[Michael Kerrisk (man-pages)]

Thanks, Heinrich.

Applied.

Cheers,

Michael


On 10/03/2014 12:06 AM, Heinrich Schuchardt wrote:
> Calling fallocate.2 does not result in inotify events.
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
>  man7/inotify.7 | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/man7/inotify.7 b/man7/inotify.7
> index a0e2528..7f45ba9 100644
> --- a/man7/inotify.7
> +++ b/man7/inotify.7
> @@ -752,6 +752,10 @@ and also the possibility that there may not be any
>  .B IN_MOVED_TO
>  event.
>  .SH BUGS
> +As of kernel 3.17, calling
> +.BR fallocate (2) 
> +does not create any inotify events.
> +
>  .\" FIXME . kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321
>  .\" implies that unmount events were buggy 2.6.11 to 2.6.36
>  .\"
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html