From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: ltp@lists.linux.it, jack@suse.com, amir73il@gmail.com
Cc: khazhy@google.com, kernel@collabora.com,
linux-ext4@vger.kernel.org, repnop@google.com,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: [PATCH v2 00/10] Test the new fanotify FAN_FS_ERROR event
Date: Tue, 26 Oct 2021 15:42:29 -0300 [thread overview]
Message-ID: <20211026184239.151156-1-krisman@collabora.com> (raw)
Hi,
Now that FAN_FS_ERROR is close to being merged, I'm sending out a new
version of the LTP tests. This version only applies the previous
feedback and updates the interface to correspond to the changes
requested on the kernel patches.
One important detail is that, for the tests to succeed, there is a
dependency on an ext4 fix I sent today:
https://lore.kernel.org/linux-ext4/20211026173302.84000-1-krisman@collabora.com/T/#u
---
Original cover letter:
FAN_FS_ERROR is a new (still unmerged) fanotify event to monitor
fileystem errors. This patchset introduces a new LTP test for this
feature.
Testing file system errors is slightly tricky, in particular because
they are mostly file system dependent. Since there are only patches for
ext4, I choose to make the test around it, since there wouldn't be much
to do with other file systems. The second challenge is how we cause the
file system errors, since there is no error injection for ext4 in Linux.
In this series, this is done by corrupting specific data in the
test device with the help of debugfs.
The FAN_FS_ERROR feature is flying around linux-ext4 and fsdevel, and
the latest version is available on the branch below:
https://gitlab.collabora.com/krisman/linux -b fanotify-notifications-v9
A proper manpage description is also available on the respective mailing
list, or in the branch below:
https://gitlab.collabora.com/krisman/man-pages.git -b fan-fs-error
Please, let me know your thoughts.
Gabriel Krisman Bertazi (10):
syscalls: fanotify: Add macro to require specific mark types
syscalls: fanotify: Add macro to require specific events
syscalls/fanotify20: Introduce helpers for FAN_FS_ERROR test
syscalls/fanotify20: Validate the generic error info
syscalls/fanotify20: Validate incoming FID in FAN_FS_ERROR
syscalls/fanotify20: Support submission of debugfs commands
syscalls/fanotify20: Create a corrupted file
syscalls/fanotify20: Test event after filesystem abort
syscalls/fanotify20: Test file event with broken inode
syscalls/fanotify20: Test capture of multiple errors
testcases/kernel/syscalls/fanotify/.gitignore | 1 +
testcases/kernel/syscalls/fanotify/fanotify.h | 72 +++-
.../kernel/syscalls/fanotify/fanotify03.c | 4 +-
.../kernel/syscalls/fanotify/fanotify10.c | 3 +-
.../kernel/syscalls/fanotify/fanotify12.c | 3 +-
.../kernel/syscalls/fanotify/fanotify20.c | 313 ++++++++++++++++++
6 files changed, 389 insertions(+), 7 deletions(-)
create mode 100644 testcases/kernel/syscalls/fanotify/fanotify20.c
--
2.33.0
WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: ltp@lists.linux.it, jack@suse.com, amir73il@gmail.com
Cc: linux-ext4@vger.kernel.org, kernel@collabora.com,
Gabriel Krisman Bertazi <krisman@collabora.com>,
khazhy@google.com, repnop@google.com
Subject: [LTP] [PATCH v2 00/10] Test the new fanotify FAN_FS_ERROR event
Date: Tue, 26 Oct 2021 15:42:29 -0300 [thread overview]
Message-ID: <20211026184239.151156-1-krisman@collabora.com> (raw)
Hi,
Now that FAN_FS_ERROR is close to being merged, I'm sending out a new
version of the LTP tests. This version only applies the previous
feedback and updates the interface to correspond to the changes
requested on the kernel patches.
One important detail is that, for the tests to succeed, there is a
dependency on an ext4 fix I sent today:
https://lore.kernel.org/linux-ext4/20211026173302.84000-1-krisman@collabora.com/T/#u
---
Original cover letter:
FAN_FS_ERROR is a new (still unmerged) fanotify event to monitor
fileystem errors. This patchset introduces a new LTP test for this
feature.
Testing file system errors is slightly tricky, in particular because
they are mostly file system dependent. Since there are only patches for
ext4, I choose to make the test around it, since there wouldn't be much
to do with other file systems. The second challenge is how we cause the
file system errors, since there is no error injection for ext4 in Linux.
In this series, this is done by corrupting specific data in the
test device with the help of debugfs.
The FAN_FS_ERROR feature is flying around linux-ext4 and fsdevel, and
the latest version is available on the branch below:
https://gitlab.collabora.com/krisman/linux -b fanotify-notifications-v9
A proper manpage description is also available on the respective mailing
list, or in the branch below:
https://gitlab.collabora.com/krisman/man-pages.git -b fan-fs-error
Please, let me know your thoughts.
Gabriel Krisman Bertazi (10):
syscalls: fanotify: Add macro to require specific mark types
syscalls: fanotify: Add macro to require specific events
syscalls/fanotify20: Introduce helpers for FAN_FS_ERROR test
syscalls/fanotify20: Validate the generic error info
syscalls/fanotify20: Validate incoming FID in FAN_FS_ERROR
syscalls/fanotify20: Support submission of debugfs commands
syscalls/fanotify20: Create a corrupted file
syscalls/fanotify20: Test event after filesystem abort
syscalls/fanotify20: Test file event with broken inode
syscalls/fanotify20: Test capture of multiple errors
testcases/kernel/syscalls/fanotify/.gitignore | 1 +
testcases/kernel/syscalls/fanotify/fanotify.h | 72 +++-
.../kernel/syscalls/fanotify/fanotify03.c | 4 +-
.../kernel/syscalls/fanotify/fanotify10.c | 3 +-
.../kernel/syscalls/fanotify/fanotify12.c | 3 +-
.../kernel/syscalls/fanotify/fanotify20.c | 313 ++++++++++++++++++
6 files changed, 389 insertions(+), 7 deletions(-)
create mode 100644 testcases/kernel/syscalls/fanotify/fanotify20.c
--
2.33.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2021-10-26 18:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 18:42 Gabriel Krisman Bertazi [this message]
2021-10-26 18:42 ` [LTP] [PATCH v2 00/10] Test the new fanotify FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-10-26 18:42 ` [PATCH v2 01/10] syscalls: fanotify: Add macro to require specific mark types Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 6:10 ` Amir Goldstein
2021-10-27 6:10 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 02/10] syscalls: fanotify: Add macro to require specific events Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 6:23 ` Amir Goldstein
2021-10-27 6:23 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 03/10] syscalls/fanotify20: Introduce helpers for FAN_FS_ERROR test Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 6:33 ` Amir Goldstein
2021-10-27 6:33 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 04/10] syscalls/fanotify20: Validate the generic error info Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 6:43 ` Amir Goldstein
2021-10-27 6:43 ` [LTP] " Amir Goldstein
2021-10-27 10:19 ` Amir Goldstein
2021-10-27 10:19 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 05/10] syscalls/fanotify20: Validate incoming FID in FAN_FS_ERROR Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 6:48 ` Amir Goldstein
2021-10-27 6:48 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 06/10] syscalls/fanotify20: Support submission of debugfs commands Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 6:49 ` Amir Goldstein
2021-10-27 6:49 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 07/10] syscalls/fanotify20: Create a corrupted file Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 6:51 ` Amir Goldstein
2021-10-27 6:51 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 08/10] syscalls/fanotify20: Test event after filesystem abort Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 9:56 ` Amir Goldstein
2021-10-27 9:56 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 09/10] syscalls/fanotify20: Test file event with broken inode Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 9:57 ` Amir Goldstein
2021-10-27 9:57 ` [LTP] " Amir Goldstein
2021-10-26 18:42 ` [PATCH v2 10/10] syscalls/fanotify20: Test capture of multiple errors Gabriel Krisman Bertazi
2021-10-26 18:42 ` [LTP] " Gabriel Krisman Bertazi
2021-10-27 10:00 ` Amir Goldstein
2021-10-27 10:00 ` [LTP] " Amir Goldstein
2021-10-29 15:03 ` Gabriel Krisman Bertazi
2021-10-29 15:03 ` [LTP] " Gabriel Krisman Bertazi
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=20211026184239.151156-1-krisman@collabora.com \
--to=krisman@collabora.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=repnop@google.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 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.