From: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
To: "Theodore Y . Ts'o " <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-btrfs@vger.kernel.org, osandov@osandov.com,
kernel-team@fb.com
Cc: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: [PATCH RFC 0/4] fscrypt changes for btrfs encryption
Date: Sat, 23 Jul 2022 20:52:24 -0400 [thread overview]
Message-ID: <cover.1658623235.git.sweettea-kernel@dorminy.me> (raw)
This is the fscrypt section of my draft patch series [1] to add
encryption support to btrfs.
Last October, Omar Sandoval sent out a design proposal for using fscrypt
with btrfs [2]. To tersely summarize the challenges laid out in the
document, btrfs supports sharing the same physical storage between
multiple files (reflinks); moving the physical location of file data
without access to the file inodes; and creating writable snapshots of
some directories (subvolumes). To allow encryption to coexist with these
features, the proposal was for btrfs to create and preserve an IV per
data block, no matter its physical location or owning inode(s), and for
btrfs to allow partially-encrypted writable snapshots of unencrypted
subvolumes.
To deal with these issues, a few changes to fscrypt are proposed:
- To enable snapshotting and then encrypting new writes to that
subvolume, a flag to allow partially encrypted directories;
- To allow filesystems to supply an IV in cases where the logical block
number and owning inode for data may change, a new policy and
interface to convey IVs from filesystem to fscrypt.
Comments, especially on the new policy and interface, appreciated!
[1] https://lore.kernel.org/linux-btrfs/cover.1658623319.git.sweettea-kernel@dorminy.me
[2] https://lore.kernel.org/linux-btrfs/YXGyq+buM79A1S0L@relinquished.localdomain/
Omar Sandoval (3):
fscrypt: expose fscrypt_nokey_name
fscrypt: add flag allowing partially-encrypted directories
fscrypt: add fscrypt_have_same_policy() to check inode's compatibility
Sweet Tea Dorminy (1):
fscrypt: Add new encryption policy for btrfs.
fs/crypto/crypto.c | 28 +++++++++++++++--
fs/crypto/fname.c | 56 ++++++++++-----------------------
fs/crypto/fscrypt_private.h | 4 +--
fs/crypto/inline_crypt.c | 20 ++++++++----
fs/crypto/keysetup.c | 5 +++
fs/crypto/policy.c | 42 ++++++++++++++++++++++++-
include/linux/fscrypt.h | 61 +++++++++++++++++++++++++++++++++++-
include/uapi/linux/fscrypt.h | 1 +
8 files changed, 166 insertions(+), 51 deletions(-)
--
2.35.1
next reply other threads:[~2022-07-24 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 0:52 Sweet Tea Dorminy [this message]
2022-07-24 0:52 ` [PATCH RFC 1/4] fscrypt: expose fscrypt_nokey_name Sweet Tea Dorminy
2022-07-24 0:52 ` [PATCH RFC 2/4] fscrypt: add flag allowing partially-encrypted directories Sweet Tea Dorminy
2022-07-25 19:49 ` Eric Biggers
2022-07-26 2:13 ` Sweet Tea Dorminy
2022-07-24 0:52 ` [PATCH RFC 3/4] fscrypt: add fscrypt_have_same_policy() to check inode's compatibility Sweet Tea Dorminy
2022-07-24 0:52 ` [PATCH RFC 4/4] fscrypt: Add new encryption policy for btrfs Sweet Tea Dorminy
2022-07-25 23:32 ` Eric Biggers
2022-07-26 2:16 ` Sweet Tea Dorminy
2022-07-26 17:45 ` David Sterba
2022-07-26 19:29 ` Eric Biggers
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.1658623235.git.sweettea-kernel@dorminy.me \
--to=sweettea-kernel@dorminy.me \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=tytso@mit.edu \
/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).