On Fri, Feb 21, 2020 at 03:50:41AM -0800, Satya Tangirala wrote:
> This patch series adds support for Inline Encryption to the block layer,
> UFS, fscrypt, f2fs and ext4.
[...]
> Changes v6 => v7:
> - Keyslot management is now done on a per-request basis rather than a
> per-bio basis.
> - Storage drivers can now specify the maximum number of bytes they
> can accept for the data unit number (DUN) for each crypto algorithm,
> and upper layers can specify the minimum number of bytes of DUN they
> want with the blk_crypto_key they send with the bio - a driver is
> only considered to support a blk_crypto_key if the driver supports at
> least as many DUN bytes as the upper layer wants. This is necessary
> because storage drivers may not support as many bytes as the
> algorithm specification dictates (for e.g. UFS only supports 8 byte
> DUNs for AES-256-XTS, even though the algorithm specification
> says DUNs are 16 bytes long).
> - Introduce SB_INLINECRYPT to keep track of whether inline encryption
> is enabled for a filesystem (instead of using an fscrypt_operation).
> - Expose keyslot manager declaration and embed it within ufs_hba to
> clean up code.
> - Make blk-crypto preclude blk-integrity.
> - Some bug fixes
> - Introduce UFSHCD_QUIRK_BROKEN_CRYPTO for UFS drivers that don't
> support inline encryption (yet)
This patchset can also be retrieved from
Repo: https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git
Tag: inline-encryption-v7
For review purposes I also created a tag
inline-encryption-v6-rebased-onto-v7-base which is the v6 patchset rebased onto
the same base commit (v5.6-rc2). So it's possible to see what changed by
git diff inline-encryption-v6-rebased-onto-v7-base..inline-encryption-v7
(Although, I had to resolve conflicts in fs/crypto/ to do the rebase, so it's
not *exactly* v6.)
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
