From: Amir Goldstein <amir73il@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/fanotify10: Add a test case for ignore mask and events on child
Date: Mon, 8 Jun 2020 09:43:29 +0300 [thread overview]
Message-ID: <20200608064329.26243-1-amir73il@gmail.com> (raw)
Add a regression test case for kernel commit 2f02fd3fa13e:
fanotify: fix ignore mask logic for events on child and on dir
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
.../kernel/syscalls/fanotify/fanotify10.c | 23 ++++++++++++++++---
1 file changed, 20 insertions(+), 3 deletions(-)
diff --git a/testcases/kernel/syscalls/fanotify/fanotify10.c b/testcases/kernel/syscalls/fanotify/fanotify10.c
index ef0807761..3cdb25a73 100644
--- a/testcases/kernel/syscalls/fanotify/fanotify10.c
+++ b/testcases/kernel/syscalls/fanotify/fanotify10.c
@@ -15,6 +15,10 @@
* This is a regression test for commit:
*
* 9bdda4e9cf2d fsnotify: fix ignore mask logic in fsnotify()
+ *
+ * Test case #16 is a regression test for commit:
+ *
+ * 2f02fd3fa13e fanotify: fix ignore mask logic for events on child...
*/
#define _GNU_SOURCE
#include "config.h"
@@ -193,7 +197,13 @@ static struct tcase {
MNT2_PATH, FANOTIFY_MOUNT,
FILE_EXEC_PATH, FAN_OPEN | FAN_OPEN_EXEC,
FAN_OPEN | FAN_OPEN_EXEC
- }
+ },
+ {
+ "ignore child exec events created on a specific mount point",
+ MOUNT_PATH, FANOTIFY_INODE,
+ MOUNT_PATH, FANOTIFY_MOUNT,
+ FILE_EXEC_PATH, FAN_OPEN_EXEC, FAN_OPEN | FAN_OPEN_EXEC
+ },
};
static int create_fanotify_groups(unsigned int n)
@@ -212,10 +222,16 @@ static int create_fanotify_groups(unsigned int n)
FAN_NONBLOCK,
O_RDONLY);
- /* Add mark for each group */
+ /*
+ * Add mark for each group.
+ *
+ * FAN_EVENT_ON_CHILD has no effect on filesystem/mount
+ * or inode mark on non-directory.
+ */
ret = fanotify_mark(fd_notify[p][i],
FAN_MARK_ADD | mark->flag,
- tc->expected_mask_without_ignore,
+ tc->expected_mask_without_ignore |
+ FAN_EVENT_ON_CHILD,
AT_FDCWD, tc->mark_path);
if (ret < 0) {
if (errno == EINVAL &&
@@ -445,6 +461,7 @@ static struct tst_test test = {
.resource_files = resource_files,
.tags = (const struct tst_tag[]) {
{"linux-git", "9bdda4e9cf2d"},
+ {"linux-git", "2f02fd3fa13e"},
{}
}
};
--
2.17.1
next reply other threads:[~2020-06-08 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 6:43 Amir Goldstein [this message]
2020-06-08 8:22 ` [LTP] [PATCH] syscalls/fanotify10: Add a test case for ignore mask and events on child Petr Vorel
2020-06-08 8:41 ` 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=20200608064329.26243-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--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