From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [PATCH 0/4] xfstests: test custom crypto data unit size
Date: Thu, 12 Oct 2023 23:13:59 -0700 [thread overview]
Message-ID: <20231013061403.138425-1-ebiggers@kernel.org> (raw)
This series adds a test for the functionality introduced by the kernel
patch
"fscrypt: support crypto data unit size less than filesystem block size"
(https://lore.kernel.org/linux-fscrypt/20230925055451.59499-6-ebiggers@kernel.org/).
It is a ciphertext verification test, as opposed to general I/O test.
This feature is not yet in mainline, but I've applied it for 6.7.
The test depends on an xfsprogs patch that adds the '-s' option to the
set_encpolicy command of xfs_io, allowing the new log2_data_unit_size
field to be set via a shell script.
As usual, the test skips itself when any prerequisite isn't met.
Eric Biggers (4):
fscrypt-crypt-util: rename block to data unit
common/rc: fix _require_xfs_io_command with digits in argument
common/encrypt: support custom data unit size
generic: add test for custom crypto data unit size
common/encrypt | 42 +++++++++++++-----
common/rc | 2 +-
src/fscrypt-crypt-util.c | 93 ++++++++++++++++++++--------------------
tests/f2fs/002 | 6 +--
tests/generic/900 | 27 ++++++++++++
tests/generic/900.out | 11 +++++
6 files changed, 121 insertions(+), 60 deletions(-)
create mode 100755 tests/generic/900
create mode 100644 tests/generic/900.out
base-commit: 59299b65ac8f15935ab45e7920cbfda8a6beffd1
--
2.42.0
next reply other threads:[~2023-10-13 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 6:13 Eric Biggers [this message]
2023-10-13 6:14 ` [PATCH 1/4] fscrypt-crypt-util: rename block to data unit Eric Biggers
2023-10-13 6:14 ` [PATCH 2/4] common/rc: fix _require_xfs_io_command with digits in argument Eric Biggers
2023-10-13 6:14 ` [PATCH 3/4] common/encrypt: support custom data unit size Eric Biggers
2023-10-13 6:14 ` [PATCH 4/4] generic: add test for custom crypto " 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=20231013061403.138425-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 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).