From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>,
Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/3] fanotify.7: fallocate creates no events
Date: Tue, 28 Oct 2014 12:44:25 +0100 [thread overview]
Message-ID: <544F8199.7040700@gmail.com> (raw)
In-Reply-To: <1412287571-5352-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
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
next prev parent reply other threads:[~2014-10-28 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 22:02 [PATCH 0/3] inotify.7, fanotify.7: fallocate triggers no event Heinrich Schuchardt
[not found] ` <1412287353-5234-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-10-02 22:05 ` [PATCH 1/3] fanotify.7: bugs still not fixed in 3.17 Heinrich Schuchardt
[not found] ` <1412287503-5304-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-10-28 11:44 ` Michael Kerrisk (man-pages)
2014-10-02 22:06 ` [PATCH 2/3] fanotify.7: fallocate creates no events Heinrich Schuchardt
[not found] ` <1412287571-5352-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-10-28 11:44 ` Michael Kerrisk (man-pages) [this message]
2014-10-02 22:06 ` [PATCH 3/3] inotify.7: fallocate does not trigger inotify events Heinrich Schuchardt
2014-10-03 8:19 ` [PATCH 1/1] fallocate: create FAN_MODIFY and IN_MODIFY events Heinrich Schuchardt
2014-10-06 14:12 ` Jan Kara
2014-10-06 19:10 ` Heinrich Schuchardt
2014-10-07 18:05 ` Jan Kara
2014-10-07 18:24 ` Heinrich Schuchardt
2014-10-14 22:43 ` Andrew Morton
2014-10-17 17:08 ` [PATCH v2 " Heinrich Schuchardt
[not found] ` <1412287587-5392-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-10-28 11:44 ` [PATCH 3/3] inotify.7: fallocate does not trigger inotify events Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544F8199.7040700@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jack-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xypron.glpk-Mmb7MZpHnFY@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.