[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211026184239.151156-9-krisman@collabora.com>
Date: Tue, 26 Oct 2021 15:42:37 -0300
From: Gabriel Krisman Bertazi <krisman@...labora.com>
To: ltp@...ts.linux.it, jack@...e.com, amir73il@...il.com
Cc: khazhy@...gle.com, kernel@...labora.com,
linux-ext4@...r.kernel.org, repnop@...gle.com,
Gabriel Krisman Bertazi <krisman@...labora.com>
Subject: [PATCH v2 08/10] syscalls/fanotify20: Test event after filesystem abort
This test monitors the error triggered after a file system abort. It
works by forcing a remount with the option "abort". This is an error
not related to a file so it is reported against the superblock with a
zero size fh.
Signed-off-by: Gabriel Krisman Bertazi <krisman@...labora.com>
---
testcases/kernel/syscalls/fanotify/fanotify20.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/testcases/kernel/syscalls/fanotify/fanotify20.c b/testcases/kernel/syscalls/fanotify/fanotify20.c
index 298bb303a810..5c5ee3c6fb74 100644
--- a/testcases/kernel/syscalls/fanotify/fanotify20.c
+++ b/testcases/kernel/syscalls/fanotify/fanotify20.c
@@ -57,6 +57,12 @@ static void do_debugfs_request(const char *dev, char *request)
SAFE_CMD(cmd, NULL, NULL);
}
+static void trigger_fs_abort(void)
+{
+ SAFE_MOUNT(tst_device->dev, MOUNT_PATH, tst_device->fs_type,
+ MS_REMOUNT|MS_RDONLY, "abort");
+}
+
static struct test_case {
char *name;
int error;
@@ -64,6 +70,13 @@ static struct test_case {
struct fanotify_fid_t *fid;
void (*trigger_error)(void);
} testcases[] = {
+ {
+ .name = "Trigger abort",
+ .trigger_error = &trigger_fs_abort,
+ .error_count = 1,
+ .error = ESHUTDOWN,
+ .fid = &null_fid,
+ },
};
int check_error_event_info_fid(struct fanotify_event_info_fid *fid,
--
2.33.0
Powered by blists - more mailing lists