fscrypt: preliminary rearrangmeents of key setup
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v6 Latest8 patches 13 repliesIn review
- v58 patches 1 replySuperseded
- v48 patches 0 repliesSuperseded
Earlier versions · 3
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v3 | 11 patches | 0 replies | Superseded | |
| v2 | 11 patches | 12 replies | Superseded | |
| v1 | 10 patches | 2 replies | Superseded |
Changes in v6 from the cover letter
- Reword 'make infos have a pointer to prepared keys' to elaborate on why it is a useful change.
Patches in v6 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | fscrypt: move inline crypt decision to info setupfs/ | +4 | 1 reply | |
| 2/8 | fscrypt: split and rename setup_file_encryption_key()fs/ | +52 | 2 replies | |
| 3/8 | fscrypt: split setup_per_mode_enc_key()fs/ | +37 | 2 replies | |
| 4/8 | fscrypt: move dirhash key setup away from IO key setupfs/ | +21 | 1 reply | |
| 5/8 | fscrypt: reduce special-casing of IV_INO_LBLK_32fs/ | +32 | 1 reply | |
| 6/8 | fscrypt: move all the shared mode key setup deeperfs/ | +88 | 2 replies | |
| 7/8 | fscrypt: make infos have a pointer to prepared keysfs/ fs/ fs/ +3 more | +18 | 1 reply | |
| 8/8 | fscrypt: make prepared keys record their typefs/ fs/ fs/ | +41 | 3 replies |
Reviews trailers per patch
7 of 8 patches have a Reviewed-by or Acked-by.
| Patch | Josef Bacik |
|---|---|
| 1/8 | R-b |
| 2/8 | R-b |
| 3/8 | R-b |
| 4/8 | R-b |
| 5/8 | |
| 6/8 | R-b |
| 7/8 | R-b |
| 8/8 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v6 0/8] fscrypt: preliminary rearrangmeents of key setup
For btrfs extent encryption, prepared keys need to be asynchronously freed after the fscrypt_info is freed. This set of various rearrangements of key setup turns the prepared key member of the info into a pointer so this is possible.
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/[email protected]/
Changelog:
v6:
- Reword 'make infos have a pointer to prepared keys' to elaborate on why it is a useful change.
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 | 357 +++++++++++++++++++++++------------- fs/crypto/keysetup_v1.c | 9 +- 6 files changed, 265 insertions(+), 144 deletions(-)
base-commit: 54d2161835d828a9663f548f61d1d9c3d3482122
Signature · 1 line
2.41.0