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>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-fscrypt@vger.kernel.org, linux-btrfs@vger.kernel.org,
kernel-team@meta.com
Cc: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: [PATCH v5 0/8] fscrypt: some rearrangements of key setup
Date: Sun, 9 Jul 2023 14:53:00 -0400 [thread overview]
Message-ID: <cover.1688927423.git.sweettea-kernel@dorminy.me> (raw)
This is a patchset designed to make key setup slightly clearer to me
ahead of rearranging it to add extent-based encryption. It is basically
a subset of my prior changeset [1] for elegance. The subsequent changes
have minor dependencies on it; I can drop this changeset if it's
preferable, although I do think it makes everything cleaner.
Patchset is built on kdave/misc-next as per base commit and needs a tiny
fixup to apply to fscrypt/for-next. It passes ext4/f2fs tests for me.
[1] https://lore.kernel.org/linux-fscrypt/cover.1681837335.git.sweettea-kernel@dorminy.me/
Changelog:
v5:
- Fixed kernel build robot complaint in patch 3.
v4:
- https://lore.kernel.org/linux-fscrypt/cover.1687988119.git.sweettea-kernel@dorminy.me/T/#t
Sweet Tea Dorminy (8):
fscrypt: move inline crypt decision to info setup
fscrypt: split and rename setup_file_encryption_key()
fscrypt: split setup_per_mode_enc_key()
fscrypt: move dirhash key setup away from IO key setup
fscrypt: reduce special-casing of IV_INO_LBLK_32
fscrypt: move all the shared mode key setup deeper
fscrypt: make infos have a pointer to prepared keys
fscrypt: make prepared keys record their type
fs/crypto/crypto.c | 2 +-
fs/crypto/fname.c | 4 +-
fs/crypto/fscrypt_private.h | 33 +++-
fs/crypto/inline_crypt.c | 4 +-
fs/crypto/keysetup.c | 375 +++++++++++++++++++++++-------------
fs/crypto/keysetup_v1.c | 9 +-
6 files changed, 274 insertions(+), 153 deletions(-)
base-commit: e0144e6be2ec62c8d874076a6292a8d83b00ee32
--
2.40.1
next reply other threads:[~2023-07-09 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 18:53 Sweet Tea Dorminy [this message]
2023-07-09 18:53 ` [PATCH v5 1/8] fscrypt: move inline crypt decision to info setup Sweet Tea Dorminy
2023-07-09 18:53 ` [PATCH v5 2/8] fscrypt: split and rename setup_file_encryption_key() Sweet Tea Dorminy
2023-07-09 18:53 ` [PATCH v5 3/8] fscrypt: split setup_per_mode_enc_key() Sweet Tea Dorminy
2023-07-09 18:53 ` [PATCH v5 4/8] fscrypt: move dirhash key setup away from IO key setup Sweet Tea Dorminy
2023-07-09 18:53 ` [PATCH v5 5/8] fscrypt: reduce special-casing of IV_INO_LBLK_32 Sweet Tea Dorminy
2023-07-09 18:53 ` [PATCH v5 6/8] fscrypt: move all the shared mode key setup deeper Sweet Tea Dorminy
2023-07-09 18:53 ` [PATCH v5 7/8] fscrypt: make infos have a pointer to prepared keys Sweet Tea Dorminy
2023-07-09 18:53 ` [PATCH v5 8/8] fscrypt: make prepared keys record their type Sweet Tea Dorminy
2023-07-24 15:31 ` Luís Henriques
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.1688927423.git.sweettea-kernel@dorminy.me \
--to=sweettea-kernel@dorminy.me \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).