b01c73ea71
Changes v5 => v6: - Blk-crypto's kernel crypto API fallback is no longer restricted to 8-byte DUNs. It's also now separately configurable from blk-crypto, and can be disabled entirely, while still allowing the kernel to use inline encryption hardware. Further, struct bio_crypt_ctx takes up less space, and no longer contains the information needed by the crypto API fallback - the fallback allocates the required memory when necessary. - Blk-crypto now supports all file content encryption modes supported by fscrypt. - Fixed bio merging logic in blk-merge.c - Fscrypt now supports inline encryption with the direct key policy, since blk-crypto now has support for larger DUNs. - Keyslot manager now uses a hashtable to lookup which keyslot contains any particular key (thanks Eric!) - Fscrypt support for inline encryption now handles filesystems with multiple underlying block devices (thanks Eric!) - Numerous cleanups Bug: 137270441 Test: refer to I26376479ee38259b8c35732cb3a1d7e15f9b05a3 Change-Id: I13e2e327e0b4784b394cb1e7cf32a04856d95f01 Link: https://lore.kernel.org/linux-block/20191218145136.172774-1-satyat@google.com/ Signed-off-by: Satya Tangirala <satyat@google.com> |
||
|---|---|---|
| .. | ||
| 00-INDEX | ||
| bfq-iosched.txt | ||
| biodoc.txt | ||
| biovecs.txt | ||
| capability.txt | ||
| cfq-iosched.txt | ||
| cmdline-partition.txt | ||
| data-integrity.txt | ||
| deadline-iosched.txt | ||
| inline-encryption.rst | ||
| ioprio.txt | ||
| kyber-iosched.txt | ||
| null_blk.txt | ||
| pr.txt | ||
| queue-sysfs.txt | ||
| request.txt | ||
| stat.txt | ||
| switching-sched.txt | ||
| writeback_cache_control.txt | ||