From: Boris Burkov <boris@bur.io>
To: fstests@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v5 0/4] tests for btrfs fsverity
Date: Mon, 13 Sep 2021 11:44:33 -0700 [thread overview]
Message-ID: <cover.1631558495.git.boris@bur.io> (raw)
This patchset provides tests for fsverity support in btrfs.
It includes modifications for generic tests to pass with btrfs as well
as new tests.
--
v5:
- more idiomatic requires structure for making efbig test generic
- make efbig test use truncate instead of pwrite for making a big file
- improve documentation for efbig test approximation
- fix underscores vs dashes in btrfs_requires_corrupt_block
- improvements in missing/redundant requires invocations
- move orphan test image file to $TEST_DIR
- make orphan test replay/snapshot device size depend on log device
instead of hard-coding it.
- rebase (signicant: no more "groups" file; use preamble)
v4:
- mark local variables
- get rid of redundant mounts and syncs
- use '_' in function names correctly
- add a test for the EFBIG case
- reduce usage of requires_btrfs_corrupt_block
- handle variable input when corrupting merkle tree
v3: rebase onto xfstests master branch
v2: pass generic tests, add logwrites test
Boris Burkov (4):
btrfs: test btrfs specific fsverity corruption
generic/574: corrupt btrfs merkle tree data
btrfs: test verity orphans with dmlogwrites
generic: test fs-verity EFBIG scenarios
common/btrfs | 5 ++
common/config | 1 +
common/verity | 38 ++++++++++
tests/btrfs/290 | 165 ++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/290.out | 25 +++++++
tests/btrfs/291 | 161 +++++++++++++++++++++++++++++++++++++++++
tests/btrfs/291.out | 2 +
tests/generic/690 | 86 ++++++++++++++++++++++
tests/generic/690.out | 7 ++
9 files changed, 490 insertions(+)
create mode 100755 tests/btrfs/290
create mode 100644 tests/btrfs/290.out
create mode 100755 tests/btrfs/291
create mode 100644 tests/btrfs/291.out
create mode 100755 tests/generic/690
create mode 100644 tests/generic/690.out
--
2.33.0
next reply other threads:[~2021-09-13 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 18:44 Boris Burkov [this message]
2021-09-13 18:44 ` [PATCH v5 1/4] btrfs: test btrfs specific fsverity corruption Boris Burkov
2021-09-13 18:44 ` [PATCH v5 2/4] generic/574: corrupt btrfs merkle tree data Boris Burkov
2021-09-13 18:44 ` [PATCH v5 3/4] btrfs: test verity orphans with dmlogwrites Boris Burkov
2021-09-13 18:44 ` [PATCH v5 4/4] generic: test fs-verity EFBIG scenarios Boris Burkov
2021-09-16 21:18 ` Eric Biggers
2022-02-08 2:20 ` [PATCH v5 0/4] tests for btrfs fsverity Eric Biggers
2022-02-08 22:34 ` Boris Burkov
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.1631558495.git.boris@bur.io \
--to=boris@bur.io \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@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).