public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/5] fanotify filesystem mark tests
Date: Fri, 16 Nov 2018 08:51:14 +0200	[thread overview]
Message-ID: <20181116065119.6912-1-amir73il@gmail.com> (raw)

Hi Cyril,

This series adds some new tests to fanotify and is also available on
my github tree [1].

Patches 1-2 re-structure tests fanotify{01,03} to iterate over the
fanotify mark types and add some missing test coverage for FAN_MARK_MOUNT.

Patches 3-5 add test coverage for the new FAN_MARK_FILESYSTEM API, that
was merged for kernel v4.20-rc1, to tests fanotify{01,03,10}.
Older kernels will report TCONF on the new test cases.

Previous patches from me pending your review:
- Add test case to fanotify09 to track a bug fix in linux-next [2]
- Enhance readahead02 to track an overlayfs regression fix in v4.19 [3]

Thanks,
Amir.

[1] https://github.com/amir73il/ltp/commits/fanotify_sb
[2] https://github.com/amir73il/ltp/commits/fanotify_ignore
[3] https://github.com/amir73il/ltp/commits/readahead_fadvise

Amir Goldstein (5):
  syscalls/fanotify01: check events also on mountpoint mark
  syscalls/fanotify03: check permission events also on mountpoint mark
  syscalls/fanotify01: add test for FAN_MARK_FILESYSTEM events
  syscalls/fanotify03: add test for FAN_MARK_FILESYSTEM permission
    events
  syscalls/fanotify10: add tests for FAN_MARK_FILESYSTEM and ignore mask

 testcases/kernel/syscalls/fanotify/fanotify.h |  3 +
 .../kernel/syscalls/fanotify/fanotify01.c     | 92 ++++++++++++-------
 .../kernel/syscalls/fanotify/fanotify03.c     | 55 +++++++++--
 .../kernel/syscalls/fanotify/fanotify10.c     | 40 +++++++-
 4 files changed, 148 insertions(+), 42 deletions(-)

-- 
2.17.1


             reply	other threads:[~2018-11-16  6:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16  6:51 Amir Goldstein [this message]
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
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=20181116065119.6912-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