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 latest related progs and kernel changesets. Marked as RFC because they're not ready to merge until all its dependencies finish landing; this is primarily to demonstrate that extent encryption, between fscrypt and btrfs, does not significantly change user-visible behavior. Changelog: RFC v2: - Reverted changes to generic/580 and generic/595 to match the new 'soft-delete' behavior introduced in v2 of kernel patchset "fscrypt: add extent encryption". (change 6) - Removed extraneous syncs/drop_caches and added copyright to new test (change 8), as per Filipe's comments. RFC v1: - https://lore.kernel.org/linux-btrfs/cover.1688076612.git.sweettea-kernel@xxxxxxxxxx/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 generic/429 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 | 59 +++++++++++++++++++++++++++++++ tests/btrfs/613.out | 13 +++++++ tests/generic/429 | 6 ++++ tests/generic/613 | 12 ++++--- 6 files changed, 169 insertions(+), 11 deletions(-) create mode 100755 tests/btrfs/613 create mode 100644 tests/btrfs/613.out base-commit: 87f90a2dae7a4adb7a0a314e27abae9aa1de78fb -- 2.40.1
|