From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] inotify.7: munmap does not lead to inotify events
Date: Sun, 25 May 2014 19:51:03 +0200 [thread overview]
Message-ID: <53822D87.5080002@gmail.com> (raw)
In-Reply-To: <1400963027-17857-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Thanks, Heinrich. Patch applied.
Cheers,
Michael
On 05/24/2014 10:23 PM, Heinrich Schuchardt wrote:
> mmap and msync were already described as not leading to inotify
> events.
>
> This patch adds munmap.
> I created and executed a test to verify this.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
> man7/inotify.7 | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/man7/inotify.7 b/man7/inotify.7
> index 55e5cab..f719614 100644
> --- a/man7/inotify.7
> +++ b/man7/inotify.7
> @@ -633,9 +633,10 @@ are not monitorable with inotify.
>
> The inotify API does not report file accesses and modifications that
> may occur because of
> -.BR mmap (2)
> +.BR mmap (2),
> +.BR msync (2),
> and
> -.BR msync (2).
> +.BR munmap (2).
>
> The inotify API identifies affected files by filename.
> However, by the time an application processes an inotify event,
>
--
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
prev parent reply other threads:[~2014-05-25 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 20:23 [PATCH 1/1] inotify.7: munmap does not lead to inotify events Heinrich Schuchardt
[not found] ` <1400963027-17857-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-05-25 17:51 ` Michael Kerrisk (man-pages) [this message]
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=53822D87.5080002@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@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.