From: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
To: fstests@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Cc: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: [PATCH 0/2] fstests: add btrfs encryption support
Date: Mon, 5 Sep 2022 20:31:36 -0400 [thread overview]
Message-ID: <cover.1662417905.git.sweettea-kernel@dorminy.me> (raw)
btrfs has several differences from other filesystems currently
integrated with fscrypt. It uses a newly proposed extent context object;
only works with direct key policies; and allows partially encrypted
directories. The design document can be found at [1].
As such, this splits a couple of tests and filters encryption policy
printing to account for different filesystems' different default
policies.
Tests for subvolume encryption, a key feature for btrfs, are not yet complete.
Necessary btrfs-progs changes are available at [2]; kernel changes
are available at [3].
[1]
https://lore.kernel.org/linux-btrfs/YXGyq+buM79A1S0L@relinquished.localdomain/
[2] https://lore.kernel.org/linux-btrfs/cover.1662420176.git.sweettea-kernel@dorminy.me
[3] https://lore.kernel.org/linux-btrfs/cover.1662417859.git.sweettea-kernel@dorminy.me
Changelog:
v2:
- Mostly rewrote and simplified the changes, as btrfs no longer requires
a separate new encryption policy.
- Added a filter function to account for different default encryption
policies.
- Split Adiantum tests, as only the direct-key variant works with
btrfs.
- https://lore.kernel.org/linux-btrfs/cover.1662417905.git.sweettea-kernel@dorminy.me
v1:
- https://lore.kernel.org/linux-btrfs/cover.1660729861.git.sweettea-kernel@dorminy.me
Sweet Tea Dorminy (2):
fstests: fscrypt: enable btrfs testing.
fstests: fscrypt: update tests of encryption contents for btrfs
common/encrypt | 141 +++++++++++++++++++++++++++++++++++++--
common/verity | 2 +-
src/fscrypt-crypt-util.c | 18 ++++-
tests/btrfs/298 | 85 +++++++++++++++++++++++
tests/btrfs/298.out | 47 +++++++++++++
tests/generic/395 | 10 ++-
tests/generic/395.out | 18 ++---
tests/generic/435 | 10 ++-
tests/generic/550 | 2 -
tests/generic/550.out | 5 --
tests/generic/576 | 3 +-
tests/generic/576.out | 6 +-
tests/generic/580 | 5 +-
tests/generic/580.out | 18 ++---
tests/generic/581 | 4 +-
tests/generic/581.out | 12 ++--
tests/generic/584 | 2 -
tests/generic/584.out | 5 --
tests/generic/720 | 26 ++++++++
tests/generic/720.out | 6 ++
tests/generic/721 | 26 ++++++++
tests/generic/721.out | 6 ++
22 files changed, 398 insertions(+), 59 deletions(-)
create mode 100755 tests/btrfs/298
create mode 100644 tests/btrfs/298.out
create mode 100755 tests/generic/720
create mode 100644 tests/generic/720.out
create mode 100755 tests/generic/721
create mode 100644 tests/generic/721.out
--
2.35.1
next reply other threads:[~2022-09-06 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 0:31 Sweet Tea Dorminy [this message]
2022-09-06 0:31 ` [PATCH 1/2] fstests: fscrypt: enable btrfs testing Sweet Tea Dorminy
2022-09-07 9:02 ` Zorro Lang
2022-09-06 0:31 ` [PATCH 2/2] fstests: fscrypt: update tests of encryption contents for btrfs Sweet Tea Dorminy
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 14:45 [PATCH 0/2] fstests: add btrfs encryption support Sweet Tea Dorminy
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.1662417905.git.sweettea-kernel@dorminy.me \
--to=sweettea-kernel@dorminy.me \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--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).