From: Josef Bacik <josef@toxicpanda.com>
To: fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] fstests: add two tests for the precontent fanotify work
Date: Wed, 4 Sep 2024 16:32:47 -0400 [thread overview]
Message-ID: <cover.1725481837.git.josef@toxicpanda.com> (raw)
Hello,
These are for the fanotify pre-content hooks feature which is posted here
https://lore.kernel.org/linux-fsdevel/cover.1725481503.git.josef@toxicpanda.com/
It adds a couple of c files to do the work necessary to setup the directories
and do the watches, and has two tests, one to validate we get the right values
on mmap and reads, and another to validate that executables work properly.
I've tested them to make sure they work properly with xfs, btrfs, ext4, and
bcachefs with my patches applied. Thanks,
Josef
Josef Bacik (2):
fstests: add a test for the precontent fanotify hooks
fstests: add a test for executing from a precontent watch directory
doc/group-names.txt | 1 +
src/Makefile | 2 +-
src/precontent/Makefile | 26 ++
src/precontent/mmap-validate.c | 227 +++++++++++++++++
src/precontent/populate.c | 188 ++++++++++++++
src/precontent/remote-fetch.c | 441 +++++++++++++++++++++++++++++++++
tests/generic/800 | 68 +++++
tests/generic/800.out | 2 +
tests/generic/801 | 64 +++++
tests/generic/801.out | 2 +
10 files changed, 1020 insertions(+), 1 deletion(-)
create mode 100644 src/precontent/Makefile
create mode 100644 src/precontent/mmap-validate.c
create mode 100644 src/precontent/populate.c
create mode 100644 src/precontent/remote-fetch.c
create mode 100644 tests/generic/800
create mode 100644 tests/generic/800.out
create mode 100644 tests/generic/801
create mode 100644 tests/generic/801.out
--
2.43.0
next reply other threads:[~2024-09-04 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 20:32 Josef Bacik [this message]
2024-09-04 20:32 ` [PATCH 1/2] fstests: add a test for the precontent fanotify hooks Josef Bacik
2024-09-05 7:17 ` Amir Goldstein
2024-09-04 20:32 ` [PATCH 2/2] fstests: add a test for executing from a precontent watch directory Josef Bacik
2024-09-05 7:21 ` Amir Goldstein
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=cover.1725481837.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).