From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/3] syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality
Date: Sun, 19 May 2019 14:39:23 +1000 [thread overview]
Message-ID: <20190519043919.GA8583@poseidon.Home> (raw)
In-Reply-To: <CAOQ4uxh7Ea02UyWeZKP5jJxhHkiTNpChH_H3=bFLNnZG4SU7-g@mail.gmail.com>
On Wed, May 15, 2019 at 05:50:03PM +0300, Amir Goldstein wrote:
> > On Fri, Apr 26, 2019 at 05:27:48PM +0200, Cyril Hrubis wrote:
> > > Hi!
> > > I've tried these tests on buildservice to check that there are no
> > > problems on slightly older distributions and found two.
> > >
> > > The first one is that we do define fallback definitions in fanotify.h
> > > but then ifdef the whole test code in #if defined(HAVE_SYS_FANOTIFY_H)
> > > so that it's efectively disabled on older distros even with fallback
> > > definitions in place. Also it's TST_TEST_TCONF() but that is just easy
> > > to fix typo. I guess that we can remove the ifdef and sys/fanotify.h
> > > include from the test sources since we conditionally include the
> > > sys/fanotify.h in the local fanotify.h already.
> >
> > OK. In that case I can write a patch that is to be applied prior to this series
> > which essentially just removes this specific preprocessor conditional directive
> > from all the source files. Would you like me to do this?
>
> If I understand the concern correctly, it is not really important
> to address now for these new tests that check functionality only available
> since kernel v5.1. It could be addressed by followup work.
OK, no problem, this is fine with me.
> > > The second one is that we fail to compile on older distributions because
> > > of missing name_to_handle_at() so we need configure check for that
> > > syscall and fallback definition in lapi/ header, or at least configure
> > > check and ifdef in the fanotify_get_fid() function. Which should be as
> > > easy as adding a name_to_handle_at line to AC_CHECK_FUNCS() in the
> > > configure.ac and using the macro from config.h.
> >
> > Sure. I've gone ahead an updated it to accommodate for this. Prior to
> > submitting through another patches series, changes can be found here:
> > https://github.com/matthewbobrowski/ltp/commit/54264db0e574d2f90e716a510fcb1da11ee174dc.
> >
> > I think we can do better and also provide a fallback definition though,
> > thoughts? Don't believe that it would take much effort.
>
> No reason to do that. Those tests will only be supported on kernel >= v5.1
> old distros are less interesting for these tests.
>
> Please post the patches for fanotify_dirent_3 branch.
OK. I've rebased fanotify_dirent_3 of upstream/master and resubmitting
the patch series now.
--
Matthew Bobrowski
next prev parent reply other threads:[~2019-05-19 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 12:49 [LTP] [PATCH v2 0/3] FAN_REPORT_FID and Directory Modification Events Matthew Bobrowski
2019-04-20 12:49 ` [LTP] [PATCH v2 1/3] syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality Matthew Bobrowski
2019-04-26 15:27 ` Cyril Hrubis
2019-04-27 4:53 ` Matthew Bobrowski
2019-05-07 7:40 ` Matthew Bobrowski
2019-05-15 14:50 ` Amir Goldstein
2019-05-19 4:39 ` Matthew Bobrowski [this message]
2019-04-20 12:50 ` [LTP] [PATCH v2 2/3] syscalls/fanotify14: new test to validate FAN_REPORT_FID interface return values Matthew Bobrowski
2019-04-20 12:50 ` [LTP] [PATCH v2 3/3] syscalls/fanotify15: verify fid for dirent events 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=20190519043919.GA8583@poseidon.Home \
--to=mbobrowski@mbobrowski.org \
--cc=ltp@lists.linux.it \
/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.