From: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
To: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
kernel-team@meta.com, ebiggers@google.com, anand.jain@oracle.com,
fdmanana@suse.com, linux-fscrypt@vger.kernel.org,
fsverity@lists.linux.dev, zlang@kernel.org
Cc: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: [RFC PATCH 0/8] fstests: add btrfs encryption testing
Date: Thu, 29 Jun 2023 18:17:15 -0400 [thread overview]
Message-ID: <cover.1688076612.git.sweettea-kernel@dorminy.me> (raw)
This is a preliminary fstests side of the btrfs encryption feature;
more tests are needed, but this gets the existing encryption tests
working with btrfs. This requires the progs and the kernel changes: [1]
[2].
Marked as RFC because they're not ready to merge until all its
dependencies finish landing.
[1] https://lore.kernel.org/linux-btrfs/cover.1688068420.git.sweettea-kernel@dorminy.me/T/#t
[2] https://lore.kernel.org/linux-btrfs/cover.1687988380.git.sweettea-kernel@dorminy.me/T/#t
Sweet Tea Dorminy (8):
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
generic/613: write some actual data for btrfs
tests: adjust encryption tests for extent encryption
common/verity: explicitly don't allow btrfs encryption
btrfs: add simple test of reflink of encrypted data
common/encrypt | 86 +++++++++++++++++++++++++++++++++++++++++----
common/verity | 4 +++
tests/btrfs/613 | 62 ++++++++++++++++++++++++++++++++
tests/btrfs/613.out | 13 +++++++
tests/generic/429 | 6 ++++
tests/generic/580 | 4 +++
tests/generic/595 | 4 +++
tests/generic/613 | 12 ++++---
8 files changed, 180 insertions(+), 11 deletions(-)
create mode 100755 tests/btrfs/613
create mode 100644 tests/btrfs/613.out
base-commit: 87f90a2dae7a4adb7a0a314e27abae9aa1de78fb
--
2.40.1
next reply other threads:[~2023-06-29 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 22:17 Sweet Tea Dorminy [this message]
2023-06-29 22:17 ` [RFC PATCH 1/8] common/encrypt: separate data and inode nonces Sweet Tea Dorminy
2023-06-29 22:17 ` [RFC PATCH 2/8] common/encrypt: add btrfs to get_encryption_*nonce Sweet Tea Dorminy
2023-06-29 22:17 ` [RFC PATCH 3/8] common/encrypt: add btrfs to get_ciphertext_filename Sweet Tea Dorminy
2023-06-29 22:17 ` [RFC PATCH 4/8] common/encrypt: enable making a encrypted btrfs filesystem Sweet Tea Dorminy
2023-06-29 22:17 ` [RFC PATCH 5/8] generic/613: write some actual data for btrfs Sweet Tea Dorminy
2023-06-29 22:17 ` [RFC PATCH 6/8] tests: adjust encryption tests for extent encryption Sweet Tea Dorminy
2023-06-29 22:17 ` [RFC PATCH 7/8] common/verity: explicitly don't allow btrfs encryption Sweet Tea Dorminy
2023-06-29 22:17 ` [RFC PATCH 8/8] btrfs: add simple test of reflink of encrypted data Sweet Tea Dorminy
2023-07-03 17:12 ` Filipe Manana
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.1688076612.git.sweettea-kernel@dorminy.me \
--to=sweettea-kernel@dorminy.me \
--cc=anand.jain@oracle.com \
--cc=ebiggers@google.com \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=kernel-team@meta.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=zlang@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.