From: Petr Vorel <pvorel@suse.cz>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: jack@suse.com, amir73il@gmail.com, repnop@google.com,
linux-ext4@vger.kernel.org, kernel@collabora.com,
khazhy@google.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 0/9] Test the new fanotify FAN_FS_ERROR event
Date: Mon, 15 Nov 2021 22:26:24 +0100 [thread overview]
Message-ID: <YZLQgDMTKBBlY8fN@pevik> (raw)
In-Reply-To: <20211029211732.386127-1-krisman@collabora.com>
Hi Gabriel, all,
I merged Matthew's v3 FAN_REPORT_PIDFD, which is for 5.15 kernel.
Could you please rebase your changes on the top of current master?
Unfortunately that means to rename fanotify21.c in all commits.
Also please: s/REQUIRE_MARK_TYPE_SUPPORTED_ON_KERNEL/REQUIRE_MARK_TYPE_SUPPORTED_BY_KERNEL/
and other changes:
diff --git testcases/kernel/syscalls/fanotify/fanotify21.c testcases/kernel/syscalls/fanotify/fanotify21.c
index 7f0154da5..44882097b 100644
--- testcases/kernel/syscalls/fanotify/fanotify21.c
+++ testcases/kernel/syscalls/fanotify/fanotify21.c
@@ -131,7 +131,7 @@ int check_error_event_info_fid(struct fanotify_event_info_fid *fid,
if (memcmp(&fid->fsid, &ex->fid->fsid, sizeof(fid->fsid))) {
tst_res(TFAIL, "%s: Received bad FSID type (%x...!=%x...)",
ex->name, FSID_VAL_MEMBER(fid->fsid, 0),
- FSID_VAL_MEMBER(ex->fid->fsid, 0));
+ ex->fid->fsid.val[0]);
return 1;
}
@@ -298,7 +298,6 @@ static struct tst_test test = {
.cleanup = cleanup,
.mount_device = 1,
.mntpoint = MOUNT_PATH,
- .all_filesystems = 0,
.needs_root = 1,
.dev_fs_type = "ext4",
.needs_cmds = (const char *[]) {
Thanks!
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: kernel@collabora.com, khazhy@google.com, repnop@google.com,
jack@suse.com, linux-ext4@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 0/9] Test the new fanotify FAN_FS_ERROR event
Date: Mon, 15 Nov 2021 22:26:24 +0100 [thread overview]
Message-ID: <YZLQgDMTKBBlY8fN@pevik> (raw)
In-Reply-To: <20211029211732.386127-1-krisman@collabora.com>
Hi Gabriel, all,
I merged Matthew's v3 FAN_REPORT_PIDFD, which is for 5.15 kernel.
Could you please rebase your changes on the top of current master?
Unfortunately that means to rename fanotify21.c in all commits.
Also please: s/REQUIRE_MARK_TYPE_SUPPORTED_ON_KERNEL/REQUIRE_MARK_TYPE_SUPPORTED_BY_KERNEL/
and other changes:
diff --git testcases/kernel/syscalls/fanotify/fanotify21.c testcases/kernel/syscalls/fanotify/fanotify21.c
index 7f0154da5..44882097b 100644
--- testcases/kernel/syscalls/fanotify/fanotify21.c
+++ testcases/kernel/syscalls/fanotify/fanotify21.c
@@ -131,7 +131,7 @@ int check_error_event_info_fid(struct fanotify_event_info_fid *fid,
if (memcmp(&fid->fsid, &ex->fid->fsid, sizeof(fid->fsid))) {
tst_res(TFAIL, "%s: Received bad FSID type (%x...!=%x...)",
ex->name, FSID_VAL_MEMBER(fid->fsid, 0),
- FSID_VAL_MEMBER(ex->fid->fsid, 0));
+ ex->fid->fsid.val[0]);
return 1;
}
@@ -298,7 +298,6 @@ static struct tst_test test = {
.cleanup = cleanup,
.mount_device = 1,
.mntpoint = MOUNT_PATH,
- .all_filesystems = 0,
.needs_root = 1,
.dev_fs_type = "ext4",
.needs_cmds = (const char *[]) {
Thanks!
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-11-15 21:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 21:17 [PATCH v3 0/9] Test the new fanotify FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-29 21:17 ` [PATCH v3 1/9] syscalls: fanotify: Add macro to require specific mark types Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-11-02 11:27 ` Matthew Bobrowski
2021-11-02 11:27 ` [LTP] " Matthew Bobrowski via ltp
2021-11-02 12:13 ` Amir Goldstein
2021-11-02 12:13 ` [LTP] " Amir Goldstein
2021-11-03 16:13 ` Petr Vorel
2021-11-03 16:13 ` Petr Vorel
2021-10-29 21:17 ` [PATCH v3 2/9] syscalls: fanotify: Add macro to require specific events Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-30 6:11 ` Amir Goldstein
2021-10-30 6:11 ` [LTP] " Amir Goldstein
2021-11-02 11:58 ` Matthew Bobrowski
2021-11-02 11:58 ` [LTP] " Matthew Bobrowski via ltp
2021-11-02 12:11 ` Amir Goldstein
2021-11-02 12:11 ` [LTP] " Amir Goldstein
2021-10-29 21:17 ` [PATCH v3 3/9] syscalls/fanotify21: Introduce FAN_FS_ERROR test Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-30 6:15 ` Amir Goldstein
2021-10-30 6:15 ` [LTP] " Amir Goldstein
2021-11-05 8:59 ` Petr Vorel
2021-11-05 8:59 ` Petr Vorel
2021-10-29 21:17 ` [PATCH v3 4/9] syscalls/fanotify21: Validate the generic error info Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-29 21:17 ` [PATCH v3 5/9] syscalls/fanotify21: Validate incoming FID in FAN_FS_ERROR Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-11-05 9:49 ` Petr Vorel
2021-11-05 9:49 ` Petr Vorel
2021-10-29 21:17 ` [PATCH v3 6/9] syscalls/fanotify21: Support submission of debugfs commands Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-29 21:17 ` [PATCH v3 7/9] syscalls/fanotify21: Create a corrupted file Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-29 21:17 ` [PATCH v3 8/9] syscalls/fanotify21: Test file event with broken inode Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-29 21:17 ` [PATCH v3 9/9] syscalls/fanotify21: Test capture of multiple errors Gabriel Krisman Bertazi
2021-10-29 21:17 ` [LTP] " Gabriel Krisman Bertazi
2021-10-30 6:21 ` [PATCH v3 0/9] Test the new fanotify FAN_FS_ERROR event Amir Goldstein
2021-10-30 6:21 ` [LTP] " Amir Goldstein
2021-11-05 10:10 ` Petr Vorel
2021-11-05 10:10 ` Petr Vorel
2021-11-05 13:02 ` Amir Goldstein
2021-11-05 13:02 ` Amir Goldstein
2021-11-05 13:10 ` Petr Vorel
2021-11-05 13:10 ` Petr Vorel
2021-11-15 21:26 ` Petr Vorel [this message]
2021-11-15 21:26 ` Petr Vorel
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=YZLQgDMTKBBlY8fN@pevik \
--to=pvorel@suse.cz \
--cc=amir73il@gmail.com \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=krisman@collabora.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.