From: Matthew Bobrowski <repnop@google.com>
To: Jan Kara <jack@suse.cz>
Cc: amir73il@gmail.com, christian.brauner@ubuntu.com,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Add pidfd support to the fanotify API
Date: Wed, 11 Aug 2021 11:22:41 +1000 [thread overview]
Message-ID: <YRMmYWHSno/IGhTN@google.com> (raw)
In-Reply-To: <20210810113348.GE18722@quack2.suse.cz>
On Tue, Aug 10, 2021 at 01:33:48PM +0200, Jan Kara wrote:
> Hello Matthew!
>
> On Sun 08-08-21 15:23:59, Matthew Bobrowski wrote:
> > This is V5 of the FAN_REPORT_PIDFD patch series. It contains the minor
> > comment/commit description fixes that were picked up by Amir in the
> > last series review [0, 1].
> >
> > LTP tests for this API change can be found here [2]. Man page updates
> > for this change can be found here [3].
> >
> > [0] https://lore.kernel.org/linux-fsdevel/CAOQ4uxhnCk+FXK_e_GA=jC_0HWO+3ZdwHSi=zCa2Kpb0NDxBSg@mail.gmail.com/
> > [1] https://lore.kernel.org/linux-fsdevel/CAOQ4uxgO3oViTSFZ0zs6brrHrmw362r1C9SQ7g6=XgRwyrzMuw@mail.gmail.com/
> > [2] https://github.com/matthewbobrowski/ltp/tree/fanotify_pidfd_v2
> > [3] https://github.com/matthewbobrowski/man-pages/tree/fanotify_pidfd_v1
> >
> > Matthew Bobrowski (5):
> > kernel/pid.c: remove static qualifier from pidfd_create()
> > kernel/pid.c: implement additional checks upon pidfd_create()
> > parameters
> > fanotify: minor cosmetic adjustments to fid labels
> > fanotify: introduce a generic info record copying helper
> > fanotify: add pidfd support to the fanotify API
>
> Thanks! I've pulled the series into my tree. Note that your fanotify21 LTP
> testcase is broken with the current kernel because 'ino' entry got added to
> fdinfo. I think having to understand all possible keys that can occur in
> fdinfo is too fragile. I understand why you want to do that but I guess the
> test would be too faulty to be practical. So I'd just ignore unknown keys
> in fdinfo for that test.
Excellent, for merging these changes!
In regards to the LTP test (fanotify21), at the time of writing I had also
shared a similar thought in the sense that it was too fragile, but wrongly
so I weighed up my decision based on the likelihood and frequency of fields
being changed/added to fdinfo. I was very wrong...
Anyway, I will fix it so that any "unknown" fields are ignored.
/M
next prev parent reply other threads:[~2021-08-11 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 5:23 [PATCH v4 0/5] Add pidfd support to the fanotify API Matthew Bobrowski
2021-08-08 5:24 ` [PATCH v4 1/5] kernel/pid.c: remove static qualifier from pidfd_create() Matthew Bobrowski
2021-08-08 5:25 ` [PATCH v4 2/5] kernel/pid.c: implement additional checks upon pidfd_create() parameters Matthew Bobrowski
2021-08-08 5:25 ` [PATCH v4 3/5] fanotify: minor cosmetic adjustments to fid labels Matthew Bobrowski
2021-08-08 5:25 ` [PATCH v4 4/5] fanotify: introduce a generic info record copying helper Matthew Bobrowski
2021-08-08 5:26 ` [PATCH v4 5/5] fanotify: add pidfd support to the fanotify API Matthew Bobrowski
2021-08-10 11:33 ` [PATCH v4 0/5] Add " Jan Kara
2021-08-11 1:22 ` Matthew Bobrowski [this message]
2021-08-16 5:03 ` 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=YRMmYWHSno/IGhTN@google.com \
--to=repnop@google.com \
--cc=amir73il@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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.