linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	eparis-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	jack-AlSwsSmVLrQ@public.gmane.org
Subject: Man pages for the fanotify API: merging of events
Date: Tue, 25 Mar 2014 16:39:47 +0100	[thread overview]
Message-ID: <5331A343.9070403@gmx.de> (raw)
In-Reply-To: <5330A257.9080100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Hello Michael,

could , please, help me to get the following fixed:

On 24.03.2014 22:23, Michael Kerrisk (man-pages) wrote:
> The pages say nothing about merging of events. Merging can happen
> for non-permission events, but not for permission events.
> Something needs to be said about this, probably in fanotify(7)
> If you are unsure of what I mean, just add the following in
> fanotify(7)
>
> .\" FIXME Document merging of events
At least there was: "The bitmask in *mask* signals which events
have occured for a single file system object. More than one of the
following flags can be set at once in the bitmask."

But this of cause does not describe that consecutive events might have 
been merged (=> Needs to be fixed in man page).

In the current coding permission events are not merged with other
events.

This feature did not exist in the kernel until two months ago, while the 
API is much older.

See patch
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=13116dfd13c8c9d60ea04ece13419af2de8e2e37

What I am unsure about is, whether the fanotify manpage should make any 
assumption that this feature will hold true for future kernel releases.

To me not merging permission events with other events seems rather to be 
a fix for some coding internal problem not something that typically 
would go into the specification.

What is your opinion?

Best regards

Heinrich Schuchardt
--
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

  parent reply	other threads:[~2014-03-25 15:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 19:53 [PATCH 1/1] Man pages for the fanotify API xypron.glpk-Mmb7MZpHnFY
     [not found] ` <1393444390-16012-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-03-14 16:42   ` Michael Kerrisk (man-pages)
     [not found]     ` <53233160.9000106-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-16 15:32       ` xypron.glpk-Mmb7MZpHnFY
     [not found]         ` <1394983959-5392-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-03-17 15:45           ` Michael Kerrisk (man-pages)
     [not found]             ` <53271880.4090100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-22 16:42               ` xypron.glpk-Mmb7MZpHnFY
     [not found]                 ` <1395506528-10026-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-03-24 21:23                   ` Michael Kerrisk (man-pages)
     [not found]                     ` <5330A257.9080100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-25 15:39                       ` Heinrich Schuchardt [this message]
     [not found]                         ` <5331A343.9070403-Mmb7MZpHnFY@public.gmane.org>
2014-03-25 16:37                           ` Man pages for the fanotify API: merging of events Jan Kara
2014-03-26 19:09                       ` [PATCH 1/1] Man pages for the fanotify API Eric Paris
2014-04-06  0:01                       ` [PATCH 0/1] Manpages " xypron.glpk-Mmb7MZpHnFY
     [not found]                         ` <1396742468-4752-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-04-06 12:18                           ` Michael Kerrisk (man-pages)
     [not found]                             ` <5341461A.3090405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-07  8:48                               ` Jan Kara
2014-04-13 14:05                               ` fanotify API: FMODE_NONOTIFY, FMODE_EXEC, FMODE_NOCMTIME Heinrich Schuchardt
2014-04-20 11:56                               ` [PATCH 1/1] Manpages for the fanotify API Heinrich Schuchardt
     [not found]                                 ` <1397994990-9068-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-04-22 14:29                                   ` Michael Kerrisk (man-pages)
     [not found]                                     ` <53567CC2.6050708-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-23 17:40                                       ` [PATCH 1/1] fanotify: add manpages Heinrich Schuchardt
     [not found]                                         ` <1398274809-6107-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-04-23 20:24                                           ` [PATCH] fanotify: add man pages Heinrich Schuchardt
     [not found]                                             ` <1398284672-7410-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-04-24 16:25                                               ` Michael Kerrisk (man-pages)
2014-04-07  8:56                           ` [PATCH 0/1] Manpages for the fanotify API Jan Kara
     [not found]                             ` <20140407085624.GB14927-+0h/O2h83AeN3ZZ/Hiejyg@public.gmane.org>
2014-04-07 18:16                               ` [PATCH 0/1] Manpages for the fanotify API: FAN_ACCESS_PERM for readdir Heinrich Schuchardt
     [not found]                                 ` <5342EB7B.4010201-Mmb7MZpHnFY@public.gmane.org>
2014-04-07 20:13                                   ` Jan Kara
2014-04-06  0:01                       ` [PATCH 1/1] Manpages for the fanotify API xypron.glpk-Mmb7MZpHnFY

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=5331A343.9070403@gmx.de \
    --to=xypron.glpk-mmb7mzphnfy@public.gmane.org \
    --cc=eparis-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jack-AlSwsSmVLrQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).