From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v5 0/4] syscalls/fanotify: FAN_REPORT_FID and Directory Modification Events
Date: Thu, 20 Jun 2019 19:57:38 +1000 [thread overview]
Message-ID: <cover.1561018312.git.mbobrowski@mbobrowski.org> (raw)
This patch series contains the changes needed to validate the new
FAN_REPORT_FID flag and directory modification event functionality
within the fanotify API.
Changes since version 4:
* Fixed problems with unbalanced file descriptor close.
* Reorded functions in the test files fanotify13, fanotify14 and
fanotify15 so that they all follow a basic template i.e.
test()
...
do_setup()
do_cleanup()
Thank you Amir for your feedback.
Amir Goldstein (1):
syscalls/fanotify13: add test coverage for fsid cache bug
Matthew Bobrowski (3):
syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality
syscalls/fanotify14: new test to validate FAN_REPORT_FID interface
return values
syscalls/fanotify15: verify fid for dirent events
configure.ac | 1 +
runtest/syscalls | 3 +
testcases/kernel/syscalls/fanotify/.gitignore | 3 +
testcases/kernel/syscalls/fanotify/fanotify.h | 81 +++++-
testcases/kernel/syscalls/fanotify/fanotify05.c | 1 +
testcases/kernel/syscalls/fanotify/fanotify13.c | 328 ++++++++++++++++++++++++
testcases/kernel/syscalls/fanotify/fanotify14.c | 176 +++++++++++++
testcases/kernel/syscalls/fanotify/fanotify15.c | 246 ++++++++++++++++++
8 files changed, 836 insertions(+), 3 deletions(-)
create mode 100644 testcases/kernel/syscalls/fanotify/fanotify13.c
create mode 100644 testcases/kernel/syscalls/fanotify/fanotify14.c
create mode 100644 testcases/kernel/syscalls/fanotify/fanotify15.c
--
2.16.4
--
Matthew Bobrowski
next reply other threads:[~2019-06-20 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 9:57 Matthew Bobrowski [this message]
2019-06-20 9:57 ` [LTP] [PATCH v5 1/4] syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality Matthew Bobrowski
2019-06-20 9:58 ` [LTP] [PATCH v5 2/4] syscalls/fanotify14: new test to validate FAN_REPORT_FID interface return values Matthew Bobrowski
2019-06-21 14:00 ` Cyril Hrubis
2019-06-23 17:13 ` Amir Goldstein
2019-06-24 8:38 ` Cyril Hrubis
2019-06-24 10:11 ` Matthew Bobrowski
2019-06-20 9:58 ` [LTP] [PATCH v5 3/4] syscalls/fanotify15: verify fid for dirent events Matthew Bobrowski
2019-06-20 9:59 ` [LTP] [PATCH v5 4/4] syscalls/fanotify13: add test coverage for fsid cache bug Amir Goldstein
2019-06-20 13:24 ` [LTP] [PATCH v5 0/4] syscalls/fanotify: FAN_REPORT_FID and Directory Modification Events Petr Vorel
2019-06-20 13:57 ` Amir Goldstein
2019-06-20 14:04 ` Amir Goldstein
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=cover.1561018312.git.mbobrowski@mbobrowski.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox