linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: mtk.manpages@gmail.com, Amir Goldstein <amir73il@gmail.com>,
	Matthew Bobrowski <mbobrowski@mbobrowski.org>,
	linux-man@vger.kernel.org, Steve Grubb <sgrubb@redhat.com>
Subject: Re: [PATCH] fanotify.7: fix outdated description
Date: Mon, 4 Jan 2021 14:29:17 +0100	[thread overview]
Message-ID: <9b9519a2-9d61-049a-a314-a9f8f880baf0@gmail.com> (raw)
In-Reply-To: <20210104115548.GC4018@quack2.suse.cz>

Hello Jan,

On 1/4/21 12:55 PM, Jan Kara wrote:
> On Wed 30-12-20 15:17:29, Michael Kerrisk (man-pages) wrote:
>> On 11/26/20 2:29 PM, Jan Kara wrote:
>>> On Thu 26-11-20 10:48:09, Michael Kerrisk (man-pages) wrote:
>>>> On 11/24/20 4:21 PM, Amir Goldstein wrote:
>>>>> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
>>>>> ---
>>>>>  man7/fanotify.7 | 7 ++++---
>>>>>  1 file changed, 4 insertions(+), 3 deletions(-)
>>>>>
>>>>> diff --git a/man7/fanotify.7 b/man7/fanotify.7
>>>>> index c4f5397e4..5804a1f30 100644
>>>>> --- a/man7/fanotify.7
>>>>> +++ b/man7/fanotify.7
>>>>> @@ -29,11 +29,12 @@ fanotify \- monitoring filesystem events
>>>>>  The fanotify API provides notification and interception of
>>>>>  filesystem events.
>>>>>  Use cases include virus scanning and hierarchical storage management.
>>>>> -Currently, only a limited set of events is supported.
>>>>> -In particular, there is no support for create, delete, and move events.
>>>>> +In the original fanotify API, only a limited set of events was supported.
>>>>> +In particular, there was no support for create, delete, and move events.
>>>>> +The support for those events was added in Linux 5.1.
>>>>>  (See
>>>>>  .BR inotify (7)
>>>>> -for details of an API that does notify those events.)
>>>>> +for details of an API that did notify those events pre Linux 5.1.)
>>>>>  .PP
>>>>>  Additional capabilities compared to the
>>>>>  .BR inotify (7)
>>>>
>>>> Thanks, Amir. Applied, with Jan's Reviewed-by.
>>>>
>>>> By the way, I see that there's still no documentation for
>>>> FAN_AUDIT/FAN_ENABLE_AUDIT, added in:
>>>>
>>>>     commit de8cd83e91bc3ee212b3e6ec6e4283af9e4ab269
>>>>     Author: Steve Grubb <sgrubb@redhat.com>
>>>>     Date:   Mon Oct 2 20:21:39 2017 -0400
>>>>
>>>>         audit: Record fanotify access control decisions
>>>>
>>>>
>>>> Can anyone help with that?
>>>
>>> Thanks for a notification. If Steve doesn't beat me to it, I'll write the
>>> doc likely next week.
>>
>> Ping!
> 
> I've already sent it and Steve has acked it [1]. So the ball is on your
> side ;).
> 
> 								Honza
> 
> [1] https://lore.kernel.org/linux-man/4619055.31r3eYUQgx@x2

I was slightly confused because you mentioned in that thread
that you might revise the patych after the comments from Alex.

Anyway, I applied now, and did some light editing. Thank you 
for the patch!

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2021-01-04 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 15:21 [PATCH] fanotify.7: fix outdated description Amir Goldstein
2020-11-25 11:53 ` Jan Kara
2020-11-26  9:48 ` Michael Kerrisk (man-pages)
2020-11-26 13:29   ` Jan Kara
2020-12-30 14:17     ` Michael Kerrisk (man-pages)
2021-01-04 11:55       ` Jan Kara
2021-01-04 13:29         ` 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=9b9519a2-9d61-049a-a314-a9f8f880baf0@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-man@vger.kernel.org \
    --cc=mbobrowski@mbobrowski.org \
    --cc=sgrubb@redhat.com \
    /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).