From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [PATCH v2 00/10] xfstests: update verity tests for non-4K block and page size
Date: Thu, 22 Dec 2022 17:05:44 -0800 [thread overview]
Message-ID: <20221223010554.281679-1-ebiggers@kernel.org> (raw)
This series updates the verity xfstests to eliminate implicit
assumptions that 'merkle_tree_block_size == fs_block_size == page_size
== 4096', and to provide some test coverage for cases where
merkle_tree_block_size differs from fs_block_size and/or page_size. It
doesn't add any new test scripts, but it does update some of the
existing test scripts to test multiple block sizes.
This goes along with my kernel patch series
"fsverity: support for non-4K pages"
(https://lore.kernel.org/linux-fsdevel/20221028224539.171818-1-ebiggers@kernel.org/T/#u).
However, it's not necessary to wait for that kernel patch series to be
applied before applying this xfstests patch series.
Changed since v1:
- Adjusted the output of generic/574, generic/575, and generic/624
slightly to avoid confusion.
Eric Biggers (10):
common/verity: add and use _fsv_can_enable()
common/verity: set FSV_BLOCK_SIZE to an appropriate value
common/verity: use FSV_BLOCK_SIZE by default
common/verity: add _filter_fsverity_digest()
generic/572: support non-4K Merkle tree block size
generic/573: support non-4K Merkle tree block size
generic/577: support non-4K Merkle tree block size
generic/574: test multiple Merkle tree block sizes
generic/624: test multiple Merkle tree block sizes
generic/575: test 1K Merkle tree block size
common/verity | 84 +++++++++++++++-----
tests/generic/572 | 21 ++---
tests/generic/572.out | 10 +--
tests/generic/573 | 8 +-
tests/generic/574 | 177 ++++++++++++++++++++++++++----------------
tests/generic/574.out | 83 ++------------------
tests/generic/575 | 57 ++++++++++----
tests/generic/575.out | 8 +-
tests/generic/577 | 24 +++---
tests/generic/577.out | 10 +--
tests/generic/624 | 119 ++++++++++++++++++++--------
tests/generic/624.out | 15 ++--
12 files changed, 348 insertions(+), 268 deletions(-)
base-commit: e263104046712af5fb5dcc7d289ac3fa5f14b764
--
2.39.0
next reply other threads:[~2022-12-23 1:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 1:05 Eric Biggers [this message]
2022-12-23 1:05 ` [PATCH v2 01/10] common/verity: add and use _fsv_can_enable() Eric Biggers
2022-12-23 1:05 ` [PATCH v2 02/10] common/verity: set FSV_BLOCK_SIZE to an appropriate value Eric Biggers
2022-12-23 1:05 ` [PATCH v2 03/10] common/verity: use FSV_BLOCK_SIZE by default Eric Biggers
2022-12-23 1:05 ` [PATCH v2 04/10] common/verity: add _filter_fsverity_digest() Eric Biggers
2022-12-23 1:05 ` [PATCH v2 05/10] generic/572: support non-4K Merkle tree block size Eric Biggers
2022-12-23 1:05 ` [PATCH v2 06/10] generic/573: " Eric Biggers
2022-12-23 1:05 ` [PATCH v2 07/10] generic/577: " Eric Biggers
2022-12-23 1:05 ` [PATCH v2 08/10] generic/574: test multiple Merkle tree block sizes Eric Biggers
2022-12-25 12:46 ` Zorro Lang
2022-12-26 5:21 ` Eric Biggers
2022-12-28 12:50 ` Theodore Ts'o
2022-12-29 16:32 ` Zorro Lang
2022-12-29 23:47 ` Eric Biggers
2022-12-23 1:05 ` [PATCH v2 09/10] generic/624: " Eric Biggers
2022-12-23 1:05 ` [PATCH v2 10/10] generic/575: test 1K Merkle tree block size Eric Biggers
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=20221223010554.281679-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fstests@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.