From: Josef Bacik <josef@toxicpanda.com>
To: fstests@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: [PATCH 00/12] fstests: fscrypt test updates
Date: Tue, 10 Oct 2023 16:25:53 -0400 [thread overview]
Message-ID: <cover.1696969376.git.josef@toxicpanda.com> (raw)
Hello,
Btrfs is adding fscrypt support, and thus requires a variety of changes to the
current fscrypt tests and infrastructure, as well as adding a few extra tests.
The bulk of the changes to the existing tests is simply breaking the v1 and v2
policy tests into two different tests, as btrfs will only support v2 policies.
The infrastructure related work is around pulling the nonce's out of the file
system in order to support the different nonce/decryption related checks.
And finally there are 3 new tests, two around reflinks and snapshots and then a
generic fsstress test.
I've tested these with ext4 and btrfs (with our patches) to make sure everything
works properly. Thanks,
Josef
Josef Bacik (5):
fstests: properly test for v1 encryption policies in encrypt tests
fstests: split generic/580 into two tests
fstests: split generic/581 into two tests
fstests: split generic/613 into two tests
fstest: add a fsstress+fscrypt test
Sweet Tea Dorminy (7):
common/encrypt: separate data and inode nonces
common/encrypt: add btrfs to get_encryption_*nonce
common/encrypt: add btrfs to get_ciphertext_filename
common/encrypt: enable making a encrypted btrfs filesystem
common/verity: explicitly don't allow btrfs encryption
btrfs: add simple test of reflink of encrypted data
btrfs: test snapshotting encrypted subvol
common/encrypt | 88 ++++++++++++++++++++++++---
common/verity | 4 ++
tests/btrfs/613 | 59 ++++++++++++++++++
tests/btrfs/613.out | 13 ++++
tests/btrfs/614 | 76 ++++++++++++++++++++++++
tests/btrfs/614.out | 111 ++++++++++++++++++++++++++++++++++
tests/f2fs/002 | 2 +-
tests/generic/580 | 118 ++++++++++++++++--------------------
tests/generic/580.out | 40 -------------
tests/generic/581 | 89 +---------------------------
tests/generic/581.out | 50 ----------------
tests/generic/593 | 1 +
tests/generic/613 | 24 +++-----
tests/generic/613.out | 5 +-
tests/generic/733 | 79 ++++++++++++++++++++++++
tests/generic/733.out | 44 ++++++++++++++
tests/generic/734 | 135 ++++++++++++++++++++++++++++++++++++++++++
tests/generic/734.out | 51 ++++++++++++++++
tests/generic/735 | 117 ++++++++++++++++++++++++++++++++++++
tests/generic/735.out | 14 +++++
tests/generic/736 | 38 ++++++++++++
tests/generic/736.out | 3 +
22 files changed, 888 insertions(+), 273 deletions(-)
create mode 100755 tests/btrfs/613
create mode 100644 tests/btrfs/613.out
create mode 100755 tests/btrfs/614
create mode 100644 tests/btrfs/614.out
create mode 100644 tests/generic/733
create mode 100644 tests/generic/733.out
create mode 100644 tests/generic/734
create mode 100644 tests/generic/734.out
create mode 100644 tests/generic/735
create mode 100644 tests/generic/735.out
create mode 100644 tests/generic/736
create mode 100644 tests/generic/736.out
--
2.41.0
next reply other threads:[~2023-10-10 20:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 20:25 Josef Bacik [this message]
2023-10-10 20:25 ` [PATCH 01/12] common/encrypt: separate data and inode nonces Josef Bacik
2023-10-17 5:20 ` Eric Biggers
2023-10-31 14:13 ` Anand Jain
2023-10-10 20:25 ` [PATCH 02/12] common/encrypt: add btrfs to get_encryption_*nonce Josef Bacik
2023-10-31 14:15 ` Anand Jain
2023-10-10 20:25 ` [PATCH 03/12] common/encrypt: add btrfs to get_ciphertext_filename Josef Bacik
2023-10-31 14:16 ` Anand Jain
2023-10-10 20:25 ` [PATCH 04/12] common/encrypt: enable making a encrypted btrfs filesystem Josef Bacik
2023-10-31 14:17 ` Anand Jain
2023-10-10 20:25 ` [PATCH 05/12] common/verity: explicitly don't allow btrfs encryption Josef Bacik
2023-10-31 14:18 ` Anand Jain
2023-10-10 20:25 ` [PATCH 06/12] btrfs: add simple test of reflink of encrypted data Josef Bacik
2023-10-31 14:04 ` Anand Jain
2023-10-10 20:26 ` [PATCH 07/12] btrfs: test snapshotting encrypted subvol Josef Bacik
2023-10-31 14:40 ` Anand Jain
2023-10-31 15:39 ` Filipe Manana
2023-11-27 14:16 ` Anand Jain
2023-11-27 15:03 ` Josef Bacik
2023-10-10 20:26 ` [PATCH 08/12] fstests: properly test for v1 encryption policies in encrypt tests Josef Bacik
2023-10-17 5:37 ` Eric Biggers
2023-11-01 11:33 ` Anand Jain
2023-10-10 20:26 ` [PATCH 09/12] fstests: split generic/580 into two tests Josef Bacik
2023-11-02 11:42 ` Anand Jain
2023-11-08 20:25 ` Josef Bacik
2023-11-22 15:41 ` Anand Jain
2023-10-10 20:26 ` [PATCH 10/12] fstests: split generic/581 " Josef Bacik
2023-10-10 20:26 ` [PATCH 11/12] fstests: split generic/613 " Josef Bacik
2023-10-10 20:26 ` [PATCH 12/12] fstest: add a fsstress+fscrypt test Josef Bacik
2023-10-17 5:23 ` Eric Biggers
2023-11-07 10:12 ` Anand Jain
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.1696969376.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=fstests@vger.kernel.org \
--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).