From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 0/3] syscalls/fanotify: FAN_REPORT_FID and Directory Modification Events
Date: Sun, 19 May 2019 15:25:13 +1000 [thread overview]
Message-ID: <cover.1558242368.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 2:
* Added an ifdef statement within fanotify_get_fid() to check
for name_to_handle_at() support.
Matthew Bobrowski (3):
syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality
syscalls/fanotify14: new test to validate FAN_REPORT_FID interface
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 ++++-
.../kernel/syscalls/fanotify/fanotify13.c | 313 ++++++++++++++++++
.../kernel/syscalls/fanotify/fanotify14.c | 171 ++++++++++
.../kernel/syscalls/fanotify/fanotify15.c | 245 ++++++++++++++
7 files changed, 814 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.21.0
--
Matthew Bobrowski
next reply other threads:[~2019-05-19 5:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 5:25 Matthew Bobrowski [this message]
2019-05-19 5:25 ` [LTP] [PATCH v3 1/3] syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality Matthew Bobrowski
2019-06-16 15:11 ` Amir Goldstein
2019-05-19 5:25 ` [LTP] [PATCH v3 2/3] syscalls/fanotify14: new test to validate FAN_REPORT_FID return values Matthew Bobrowski
2019-05-19 5:26 ` [LTP] [PATCH v3 3/3] syscalls/fanotify15: verify fid for dirent events Matthew Bobrowski
2019-06-03 8:53 ` [LTP] [PATCH v3 0/3] syscalls/fanotify: FAN_REPORT_FID and Directory Modification Events 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.1558242368.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