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 4/8] common/encrypt: enable making a encrypted btrfs filesystem
Date: Thu, 29 Jun 2023 18:17:19 -0400 [thread overview]
Message-ID: <ade755dbe4a98c52acaa88fcf9799c7c9976d7ca.1688076612.git.sweettea-kernel@dorminy.me> (raw)
In-Reply-To: <cover.1688076612.git.sweettea-kernel@dorminy.me>
Signed-off-by: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
---
common/encrypt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/common/encrypt b/common/encrypt
index 2c1925da..1372af66 100644
--- a/common/encrypt
+++ b/common/encrypt
@@ -153,6 +153,9 @@ _scratch_mkfs_encrypted()
# erase the UBI volume; reformated automatically on next mount
$UBIUPDATEVOL_PROG ${SCRATCH_DEV} -t
;;
+ btrfs)
+ _scratch_mkfs
+ ;;
ceph)
_scratch_cleanup_files
;;
@@ -168,6 +171,9 @@ _scratch_mkfs_sized_encrypted()
ext4|f2fs)
MKFS_OPTIONS="$MKFS_OPTIONS -O encrypt" _scratch_mkfs_sized $*
;;
+ btrfs)
+ _scratch_mkfs_sized $*
+ ;;
*)
_notrun "Filesystem $FSTYP not supported in _scratch_mkfs_sized_encrypted"
;;
--
2.40.1
next prev parent reply other threads:[~2023-06-29 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 22:17 [RFC PATCH 0/8] fstests: add btrfs encryption testing Sweet Tea Dorminy
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 ` Sweet Tea Dorminy [this message]
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=ade755dbe4a98c52acaa88fcf9799c7c9976d7ca.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).