From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/5] syscalls/fanotify01: check events also on mountpoint mark
Date: Wed, 21 Nov 2018 13:01:03 +0100 [thread overview]
Message-ID: <20181121120103.GB2954@rei> (raw)
In-Reply-To: <20181116065119.6912-2-amir73il@gmail.com>
Hi!
> /* This event should be ignored */
> @@ -181,13 +200,13 @@ void test01(void)
>
> /* Now remove open and close from ignored mask */
> if (fanotify_mark(fd_notify,
> - FAN_MARK_REMOVE | FAN_MARK_IGNORED_MASK,
> + FAN_MARK_REMOVE | mark->flag | FAN_MARK_IGNORED_MASK,
> FAN_OPEN | FAN_CLOSE, AT_FDCWD, fname) < 0) {
> tst_brk(TBROK | TERRNO,
> - "fanotify_mark (%d, FAN_MARK_REMOVE | "
> - "FAN_MARK_IGNORED_MASK, FAN_OPEN | "
> - "FAN_CLOSE, AT_FDCWD, %s) failed", fd_notify,
> - fname);
> + "fanotify_mark (%d, FAN_MARK_REMOVE | %s | "
> + "FAN_MARK_IGNORED_MASK, FAN_OPEN | FAN_CLOSE, "
> + "AT_FDCWD, %s) failed", fd_notify,
> + mark->name, fname);
> }
>
> SAFE_CLOSE(fd);
> @@ -283,12 +302,13 @@ pass:
>
> }
> /* Remove mark to clear FAN_MARK_IGNORED_SURV_MODIFY */
> - if (fanotify_mark(fd_notify, FAN_MARK_REMOVE, FAN_ACCESS | FAN_MODIFY |
> - FAN_CLOSE | FAN_OPEN, AT_FDCWD, fname) < 0) {
> + if (fanotify_mark(fd_notify, FAN_MARK_REMOVE | mark->flag,
> + FAN_ACCESS | FAN_MODIFY | FAN_CLOSE | FAN_OPEN,
> + AT_FDCWD, fname) < 0) {
> tst_brk(TBROK | TERRNO,
> - "fanotify_mark (%d, FAN_MARK_REMOVE, FAN_ACCESS | "
> + "fanotify_mark (%d, FAN_MARK_REMOVE | %s, FAN_ACCESS | "
> "FAN_MODIFY | FAN_CLOSE | FAN_OPEN, AT_FDCWD, %s) "
> - "failed", fd_notify, fname);
> + "failed", fd_notify, mark->name, fname);
> }
> }
>
> @@ -296,8 +316,6 @@ static void setup(void)
> {
> sprintf(fname, "tfile_%d", getpid());
> SAFE_FILE_PRINTF(fname, "1");
> -
> - fd_notify = SAFE_FANOTIFY_INIT(FAN_CLASS_NOTIF, O_RDONLY);
I've added SAFE_CLOSE(fd_notify) here so that we do not use all
available file descriptors with large enough -i parameter and pushed.
I do wonder what is the reason to move the fanotify_init() from setup
the the test_fanotify(), is there a problem with recycling the same fd
for different tests?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-11-21 12:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 6:51 [LTP] [PATCH 0/5] fanotify filesystem mark tests Amir Goldstein
2018-11-16 6:51 ` [LTP] [PATCH 1/5] syscalls/fanotify01: check events also on mountpoint mark Amir Goldstein
2018-11-21 12:01 ` Cyril Hrubis [this message]
2018-11-21 16:18 ` Amir Goldstein
2018-11-22 16:06 ` Cyril Hrubis
2018-11-22 16:57 ` Amir Goldstein
2018-11-16 6:51 ` [LTP] [PATCH 2/5] syscalls/fanotify03: check permission " Amir Goldstein
2018-11-21 12:26 ` Cyril Hrubis
2018-11-16 6:51 ` [LTP] [PATCH 3/5] syscalls/fanotify01: add test for FAN_MARK_FILESYSTEM events Amir Goldstein
2018-11-21 13:00 ` Cyril Hrubis
2018-11-16 6:51 ` [LTP] [PATCH 4/5] syscalls/fanotify03: add test for FAN_MARK_FILESYSTEM permission events Amir Goldstein
2018-11-21 13:14 ` Cyril Hrubis
2018-11-21 16:36 ` Amir Goldstein
2018-11-21 17:10 ` Amir Goldstein
2018-11-22 16:03 ` Cyril Hrubis
2018-11-16 6:51 ` [LTP] [PATCH 5/5] syscalls/fanotify10: add tests for FAN_MARK_FILESYSTEM and ignore mask Amir Goldstein
2018-11-21 13:27 ` Cyril Hrubis
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=20181121120103.GB2954@rei \
--to=chrubis@suse.cz \
--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