ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Matthew Bobrowski <repnop@google.com>, Jan Kara <jack@suse.cz>,
	ltp@lists.linux.it
Subject: [LTP] [PATCH 0/5] Fanotify tests for FAN_MARK_EVICTABLE
Date: Mon, 13 Jun 2022 17:38:21 +0300	[thread overview]
Message-ID: <20220613143826.1328830-1-amir73il@gmail.com> (raw)

Hi Petr,

FAN_MARK_EVICTABLE feature was merge in v5.19-rc1.

Here are the tests for it.

inotify12 is a test for an unrelated fix.

Note that fanotify23 is run on ext2.
That is because, I could not find a way to reliably evict
an inode on any filesystem and the rain dance I did with
vfs_cache_pressure and drop_caches works reliably with ext2
on my test setup.

If that turns out not to work on other systems, we will need
to re-think of a more aggressive way to force inode eviction.

Thanks,
Amir.

Amir Goldstein (5):
  syscalls/inotify12: Introduce test for inotify mask flags
  syscalls/fanotify23: Introduce FAN_MARK_EVICTABLE test
  syscalls/fanotify10: Watch directory that is not the mount path
  syscalls/fanotify10: Mount cycle between test cases
  syscalls/fanotify10: Add test cases for evictable ignore mark

 runtest/syscalls                              |   2 +
 testcases/kernel/syscalls/fanotify/.gitignore |   1 +
 testcases/kernel/syscalls/fanotify/fanotify.h |   4 +
 .../kernel/syscalls/fanotify/fanotify10.c     | 131 +++++++--
 .../kernel/syscalls/fanotify/fanotify23.c     | 258 ++++++++++++++++++
 testcases/kernel/syscalls/inotify/.gitignore  |   1 +
 testcases/kernel/syscalls/inotify/inotify12.c | 168 ++++++++++++
 7 files changed, 546 insertions(+), 19 deletions(-)
 create mode 100644 testcases/kernel/syscalls/fanotify/fanotify23.c
 create mode 100644 testcases/kernel/syscalls/inotify/inotify12.c

-- 
2.25.1


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2022-06-13 14:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 14:38 Amir Goldstein [this message]
2022-06-13 14:38 ` [LTP] [PATCH 1/5] syscalls/inotify12: Introduce test for inotify mask flags Amir Goldstein
2022-06-13 14:58   ` Amir Goldstein
2022-06-13 15:23     ` Petr Vorel
2022-06-13 16:03       ` Amir Goldstein
2022-06-13 16:05         ` Petr Vorel
2022-06-13 15:48   ` Petr Vorel
2022-06-14 10:19   ` Jan Kara
2022-06-14 11:28     ` Petr Vorel
2022-06-13 14:38 ` [LTP] [PATCH 2/5] syscalls/fanotify23: Introduce FAN_MARK_EVICTABLE test Amir Goldstein
2022-06-14 10:19   ` Jan Kara
2022-06-16  8:36   ` Petr Vorel
2022-06-16  8:50     ` Amir Goldstein
2022-06-16 13:28       ` Petr Vorel
2022-06-13 14:38 ` [LTP] [PATCH 3/5] syscalls/fanotify10: Watch directory that is not the mount path Amir Goldstein
2022-06-14 10:26   ` Jan Kara
2022-06-14 11:10     ` Amir Goldstein
2022-06-16 13:31       ` Petr Vorel
2022-06-16 13:46         ` Amir Goldstein
2022-06-16 16:57           ` Petr Vorel
2022-06-13 14:38 ` [LTP] [PATCH 4/5] syscalls/fanotify10: Mount cycle between test cases Amir Goldstein
2022-06-14 10:47   ` Jan Kara
2022-06-13 14:38 ` [LTP] [PATCH 5/5] syscalls/fanotify10: Add test cases for evictable ignore mark Amir Goldstein
2022-06-14 13:04   ` Jan Kara
2022-06-30  6:27   ` Jan Stancek
2022-06-30  8:20     ` Amir Goldstein
2022-07-07 12:49       ` Jan Stancek
2022-07-09 10:09         ` Amir Goldstein
2022-07-12  8:19           ` Jan Stancek
2022-08-24 15:24             ` Jan Kara
2022-08-24 18:13               ` Amir Goldstein
2022-08-25  9:33                 ` Jan Kara
2022-08-25 12:53               ` Jan Stancek
2022-08-25 13:47                 ` Amir Goldstein
2022-08-25 14:03                   ` Jan Kara

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=20220613143826.1328830-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).