From: Matthew Bobrowski <repnop@google.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>, Jan Kara <jack@suse.cz>,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [PATCH 0/1] fanotify: Document FAN_REPORT_PIDFD Feature
Date: Mon, 22 Nov 2021 22:18:53 +1100 [thread overview]
Message-ID: <YZt8nVu1Ze4vHGdr@google.com> (raw)
In-Reply-To: <CAOQ4uxhUpnDVT6T-aGz2B_XUpRojJhVZG8Fw6XNegsWzXt+pDw@mail.gmail.com>
On Sat, Nov 20, 2021 at 12:36:26PM +0200, Amir Goldstein wrote:
> On Wed, Oct 27, 2021 at 12:28 PM Matthew Bobrowski <repnop@google.com> wrote:
> >
> > Hi Michael,
> >
> > This patch series documents the new FAN_REPORT_PIDFD feature that is
> > available from v5.15.
> >
> > Note that this patch series is diffbased against the FANOTIFY_UNPRIV
> > [0, 1] man page updates that are yet to be merged with upstream. That
> > said, if you could please merge the FANOTIFY_UNPRIV updates first
> > followed by the FAN_REPORT_PIDFD updates, that would be much
> > appreciated.
> >
> > [0] https://lore.kernel.org/linux-man/20210318160817.3586288-1-amir73il@gmail.com/
> > [1] https://github.com/amir73il/man-pages/commits/fanotify_unpriv
> >
>
> Alejandro,
>
> Is there any changes of getting those long due 5.13 fanotify update
> patches merged?
>
> Matthew,
>
> For v2 please base your own fanotify_pidfd branch on top of fanotify_unpriv
> (I just rebased it to master again) and provide a branch, that Gabriel
> and I could
> base the next man page updates on.
>
> Currently, neither your fanotify_pidfd patch nor Gabriel's fan-fs-error patch
> conflict with fanotify_unpriv changes, but fan-fs-error does have conflicts
> with fanotify_pidfd.
ACK.
As per request, v2 of the FAN_REPORT_PIDFD documentation can be found
here [0].
The branch fanotify_pidfd_v2 is based off your fanotify_unpriv
branch. I'd like to post through this series at some point tomorrow,
so if you could PTAL in the interim, that'd be appreciated.
I've incorporated the explicit documentation of the
fanotify_event_info_header structure, rather than duplicating field
explanations of such a structure across each information record types
as we had discussed.
[0] https://github.com/matthewbobrowski/man-pages/tree/fanotify_pidfd_v2
/M
next prev parent reply other threads:[~2021-11-22 11:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 9:28 [PATCH 0/1] fanotify: Document FAN_REPORT_PIDFD Feature Matthew Bobrowski
2021-10-27 9:28 ` [PATCH 1/1] Document the new fanotify initialization flag FAN_REPORT_PIDFD Matthew Bobrowski
2021-10-27 9:59 ` Jan Kara
2021-10-27 10:14 ` Amir Goldstein
2021-11-01 21:02 ` Matthew Bobrowski
2021-11-02 6:31 ` Amir Goldstein
2021-11-02 10:12 ` Alejandro Colomar (man-pages)
2021-11-20 12:19 ` Amir Goldstein
2021-11-22 11:23 ` Matthew Bobrowski
2021-11-20 10:36 ` [PATCH 0/1] fanotify: Document FAN_REPORT_PIDFD Feature Amir Goldstein
2021-11-20 13:32 ` Alejandro Colomar (man-pages)
2021-11-20 14:45 ` Amir Goldstein
2021-11-20 16:51 ` Alejandro Colomar (man-pages)
2021-11-20 17:04 ` Amir Goldstein
2021-11-22 11:18 ` Matthew Bobrowski [this message]
2021-11-22 13:37 ` Amir Goldstein
2021-11-23 5:15 ` Matthew Bobrowski
2022-03-17 10:09 ` Amir Goldstein
2022-03-17 21:34 ` Matthew Bobrowski
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=YZt8nVu1Ze4vHGdr@google.com \
--to=repnop@google.com \
--cc=alx.manpages@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=krisman@collabora.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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