Inline Encryption Support
Subsystems (8)
v9 cover Inline Encryption Support
This patch series adds support for Inline Encryption to the block layer, UFS, fscrypt, f2fs and ext4.
Note that the patches in this series for the block layer (i.e. patches 1, 2, 3 and 4) can be applied independently of the subsequent patches in this series.
Inline Encryption hardware allows software to specify an encryption context (an encryption key, crypto algorithm, data unit num, data unit size, etc.) along with a data transfer request to a storage device, and the inline encryption hardware will use that context to en/decrypt the data. The inline encryption hardware is part of the storage device, and it conceptually sits on the data path between system memory and the storage device. Inline Encryption hardware has become increasingly common, and we want to support it in the kernel.
Inline Encryption hardware implementations often function around the concept of a limited number of "keyslots", which can hold an encryption context each. The storage device can be directed to en/decrypt any particular request with the encryption context stored in any particular keyslot.
Patch 1 introduces a Keyslot Manager to efficiently manage keyslots. The keyslot manager also functions as the interface that blk-crypto (introduced in Patch 2), will use to program keys into inline encryption hardware. For more information on the Keyslot Manager, refer to documentation found in block/keyslot-manager.c and linux/keyslot-manager.h.
Patch 2 adds the block layer changes for inline encryption support. It introduces struct bio_crypt_ctx, and a ptr to one in struct bio, which allows struct bio to represent an encryption context that can be passed down the storage stack from the filesystem layer to the storage driver.
Patch 3 precludes inline encryption support in a device whenever it supports blk-integrity, because there is currently no known hardware that supports both features, and it is not completely straightfoward to support both of them properly, and doing it improperly might result in leaks of information about the plaintext.
Patch 4 introduces blk-crypto-fallback - a kernel crypto API fallback for blk-crypto to use when inline encryption hardware isn't present. This allows filesystems to specify encryption contexts for bios without having to worry about whether the underlying hardware has inline encryption support, and allows for testing without real hardware inline encryption support. This fallback is separately configurable from blk-crypto, and can be disabled if desired while keeping inline encryption support. It may also be possible to remove file content en/decryption from fscrypt and simply use blk-crypto-fallback in a future patch. For more details on blk-crypto and the fallback, refer to Documentation/block/inline-encryption.rst.
Patches 5-7 add support for inline encryption into the UFS driver according to the JEDEC UFS HCI v2.1 specification. Inline encryption support for other drivers (like eMMC) may be added in the same way - the device driver should set up a Keyslot Manager in the device's request_queue (refer to the UFS crypto additions in ufshcd-crypto.c and ufshcd.c for an example).
Patch 8 adds the SB_INLINECRYPT mount flag to the fs layer, which filesystems must set to indicate that they want to use blk-crypto for en/decryption of file contents.
Patch 9 adds support to fscrypt - to use inline encryption with fscrypt, the filesystem must be mounted with '-o inlinecrypt' - when this option is specified, the contents of any AES-256-XTS encrypted file will be encrypted using blk-crypto.
Patches 10 and 11 add support to f2fs and ext4 respectively, so that we have a complete stack that can make use of inline encryption.
The patches were tested running kvm-xfstests, by specifying the introduced "inlinecrypt" mount option, so that en/decryption happens with the blk-crypto fallback. The patches were also tested on a Pixel 4 with UFS hardware that has support for inline encryption.
There have been a few patch sets addressing Inline Encryption Support in the past. Briefly, this patch set differs from those as follows:
1) "crypto: qce: ice: Add support for Inline Crypto Engine" is specific to certain hardware, while our patch set's Inline Encryption support for UFS is implemented according to the JEDEC UFS specification.
2) "scsi: ufs: UFS Host Controller crypto changes" registers inline encryption support as a kernel crypto algorithm. Our patch views inline encryption as being fundamentally different from a generic crypto provider (in that inline encryption is tied to a device), and so does not use the kernel crypto API to represent inline encryption hardware.
3) "scsi: ufs: add real time/inline crypto support to UFS HCD" requires the device mapper to work - our patch does not.
Changes v8 => v9:
- Don't open code bio_has_crypt_ctx into callers of blk-crypto functions.
- Lots of cleanups
Changes v7 => v8:
- Pass a struct blk_ksm_keyslot * around instead of slot numbers which simplifies some functions and passes around arguments with better types
- Make bios with no encryption context avoid making calls into blk-crypto by checking for the presence of bi_crypt_context before making the call
- Make blk-integrity preclude inline encryption support at probe time
- Many many cleanups
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)
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
Changes v4 => v5:
- The fscrypt patch has been separated into 2. The first adds support for the IV_INO_LBLK_64 policy (which was called INLINE_CRYPT_OPTIMIZED in past versions of this series). This policy is now purely an on disk format, and doesn't dictate whether blk-crypto is used for file content encryption or not. Instead, this is now decided based on the "inlinecrypt" mount option.
- Inline crypto key eviction is now handled by blk-crypto instead of fscrypt.
- More refactoring.
Changes v3 => v4:
- Fixed the issue with allocating crypto_skcipher in blk_crypto_keyslot_program.
- bio_crypto_alloc_ctx is now mempool backed.
- In f2fs, a bio's bi_crypt_context is now set up when the bio is allocated, rather than just before the bio is submitted - this fixes bugs in certain cases, like when an encrypted block is being moved without decryption.
- Lots of refactoring and cleanup of blk-crypto - thanks Eric!
Changes v2 => v3:
- Overhauled keyslot manager's get keyslot logic and optimized LRU.
- Block crypto en/decryption fallback now supports data unit sizes that divide the bvec length (instead of requiring each bvec's length to be the same as the data unit size).
- fscrypt master key is now keyed additionally by super_block and ci_ctfm != NULL.
- all references of "hw encryption" are replaced by inline encryption.
- address various other review comments from Eric.
Changes v1 => v2:
- Block layer and UFS changes are split into 3 patches each.
- We now only have a ptr to a struct bio_crypt_ctx in struct bio, instead of the struct itself.
- struct bio_crypt_ctx no longer has flags.
- blk-crypto now correctly handles the case when it fails to init (because of insufficient memory), but kernel continues to boot.
- ufshcd-crypto now works on big endian cpus.
- Many cleanups.
Eric Biggers (1):
ext4: add inline encryption support
Satya Tangirala (10):
block: Keyslot Manager for Inline Encryption
block: Inline encryption support for blk-mq
block: Make blk-integrity preclude hardware inline encryption
block: blk-crypto-fallback for Inline Encryption
scsi: ufs: UFS driver v2.1 spec crypto additions
scsi: ufs: UFS crypto API
scsi: ufs: Add inline encryption support to UFS
fs: introduce SB_INLINECRYPT
fscrypt: add inline encryption support
f2fs: add inline encryption support
Documentation/admin-guide/ext4.rst | 6 + Documentation/block/index.rst | 1 + Documentation/block/inline-encryption.rst | 195 +++++++ Documentation/filesystems/f2fs.txt | 6 + block/Kconfig | 17 + block/Makefile | 2 + block/bio-integrity.c | 3 + block/bio.c | 6 + block/blk-core.c | 20 +- block/blk-crypto-fallback.c | 666 ++++++++++++++++++++++ block/blk-crypto-internal.h | 197 +++++++ block/blk-crypto.c | 408 +++++++++++++ block/blk-integrity.c | 7 + block/blk-map.c | 1 + block/blk-merge.c | 11 + block/blk-mq.c | 12 + block/blk.h | 4 + block/bounce.c | 2 + block/keyslot-manager.c | 396 +++++++++++++ drivers/md/dm.c | 3 + drivers/scsi/ufs/Kconfig | 9 + drivers/scsi/ufs/Makefile | 1 + drivers/scsi/ufs/ufshcd-crypto.c | 226 ++++++++ drivers/scsi/ufs/ufshcd-crypto.h | 62 ++ drivers/scsi/ufs/ufshcd.c | 46 +- drivers/scsi/ufs/ufshcd.h | 23 + drivers/scsi/ufs/ufshci.h | 67 ++- fs/buffer.c | 7 +- fs/crypto/Kconfig | 6 + fs/crypto/Makefile | 1 + fs/crypto/bio.c | 51 ++ fs/crypto/crypto.c | 2 +- fs/crypto/fname.c | 4 +- fs/crypto/fscrypt_private.h | 120 +++- fs/crypto/inline_crypt.c | 328 +++++++++++ fs/crypto/keyring.c | 4 +- fs/crypto/keysetup.c | 92 ++- fs/crypto/keysetup_v1.c | 16 +- fs/ext4/inode.c | 4 +- fs/ext4/page-io.c | 6 +- fs/ext4/readpage.c | 11 +- fs/ext4/super.c | 9 + fs/f2fs/compress.c | 2 +- fs/f2fs/data.c | 68 ++- fs/f2fs/super.c | 32 ++ fs/proc_namespace.c | 1 + include/linux/blk-crypto.h | 129 +++++ include/linux/blk_types.h | 6 + include/linux/blkdev.h | 41 ++ include/linux/fs.h | 1 + include/linux/fscrypt.h | 57 ++ include/linux/keyslot-manager.h | 107 ++++ 52 files changed, 3413 insertions(+), 89 deletions(-) create mode 100644 Documentation/block/inline-encryption.rst create mode 100644 block/blk-crypto-fallback.c create mode 100644 block/blk-crypto-internal.h create mode 100644 block/blk-crypto.c create mode 100644 block/keyslot-manager.c create mode 100644 drivers/scsi/ufs/ufshcd-crypto.c create mode 100644 drivers/scsi/ufs/ufshcd-crypto.h create mode 100644 fs/crypto/inline_crypt.c create mode 100644 include/linux/blk-crypto.h create mode 100644 include/linux/keyslot-manager.h
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
PATCH v9 1/11 block: Keyslot Manager for Inline Encryption
Inline Encryption hardware allows software to specify an encryption context (an encryption key, crypto algorithm, data unit num, data unit size) along with a data transfer request to a storage device, and the inline encryption hardware will use that context to en/decrypt the data. The inline encryption hardware is part of the storage device, and it conceptually sits on the data path between system memory and the storage device.
Inline Encryption hardware implementations often function around the concept of "keyslots". These implementations often have a limited number of "keyslots", each of which can hold a key (we say that a key can be "programmed" into a keyslot). Requests made to the storage device may have a keyslot and a data unit number associated with them, and the inline encryption hardware will en/decrypt the data in the requests using the key programmed into that associated keyslot and the data unit number specified with the request.
As keyslots are limited, and programming keys may be expensive in many implementations, and multiple requests may use exactly the same encryption contexts, we introduce a Keyslot Manager to efficiently manage keyslots.
We also introduce a blk_crypto_key, which will represent the key that's programmed into keyslots managed by keyslot managers. The keyslot manager also functions as the interface that upper layers will use to program keys into inline encryption hardware. For more information on the Keyslot Manager, refer to documentation found in block/keyslot-manager.c and linux/keyslot-manager.h.
--- block/Kconfig | 7 + block/Makefile | 1 + block/keyslot-manager.c | 377 ++++++++++++++++++++++++++++++++ include/linux/blk-crypto.h | 45 ++++ include/linux/blkdev.h | 6 + include/linux/keyslot-manager.h | 107 +++++++++ 6 files changed, 543 insertions(+) create mode 100644 block/keyslot-manager.c create mode 100644 include/linux/blk-crypto.h create mode 100644 include/linux/keyslot-manager.h
block/Kconfig +7 -0
@@ -185,6 +185,13 @@ config BLK_SED_OPAL Enabling this option enables users to setup/unlock/lock Locking ranges for SED devices using the Opal protocol. +config BLK_INLINE_ENCRYPTION + bool "Enable inline encryption support in block layer" + help + Build the blk-crypto subsystem. Enabling this lets the + block layer handle encryption, so users can take + advantage of inline encryption hardware if present. + menu "Partition Types" source "block/partitions/Kconfig"
block/Makefile +1 -0
@@ -37,3 +37,4 @@ obj-$(CONFIG_BLK_DEBUG_FS) += blk-mq-debugfs.o obj-$(CONFIG_BLK_DEBUG_FS_ZONED)+= blk-mq-debugfs-zoned.o obj-$(CONFIG_BLK_SED_OPAL) += sed-opal.o obj-$(CONFIG_BLK_PM) += blk-pm.o +obj-$(CONFIG_BLK_INLINE_ENCRYPTION) += keyslot-manager.o
block/keyslot-manager.c new file +377 -0
377 lines not on this page · raw message
include/linux/blk-crypto.h new file +45 -0
45 lines not on this page · raw message
include/linux/blkdev.h +6 -0
@@ -43,6 +43,7 @@ struct pr_ops;struct rq_qos ;struct blk_queue_stats ;struct blk_stat_callback ; +struct blk_keyslot_manager ;#define BLKDEV_MIN_RQ 4#define BLKDEV_MAX_RQ 128/* Default maximum */
@@ -474,6 +475,11 @@ struct request_queue {unsigned int dma_pad_mask;unsigned int dma_alignment; +#ifdef CONFIG_BLK_INLINE_ENCRYPTION +/* Inline crypto capabilities */ +struct blk_keyslot_manager *ksm; +#endif +unsigned int rq_timeout;int poll_nsec;
include/linux/keyslot-manager.h new file +107 -0
107 lines not on this page · raw message
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerRe: [PATCH v9 01/11] block: Keyslot Manager for Inline Encryption
Quoted 27 lines · Satya Tangirala
Inline Encryption hardware allows software to specify an encryption context (an encryption key, crypto algorithm, data unit num, data unit size) along with a data transfer request to a storage device, and the inline encryption hardware will use that context to en/decrypt the data. The inline encryption hardware is part of the storage device, and it conceptually sits on the data path between system memory and the storage device.
Inline Encryption hardware implementations often function around the concept of "keyslots". These implementations often have a limited number of "keyslots", each of which can hold a key (we say that a key can be "programmed" into a keyslot). Requests made to the storage device may have a keyslot and a data unit number associated with them, and the inline encryption hardware will en/decrypt the data in the requests using the key programmed into that associated keyslot and the data unit number specified with the request.
As keyslots are limited, and programming keys may be expensive in many implementations, and multiple requests may use exactly the same encryption contexts, we introduce a Keyslot Manager to efficiently manage keyslots.
We also introduce a
blk_crypto_key, which will represent the key that's programmed into keyslots managed by keyslot managers. The keyslot manager also functions as the interface that upper layers will use to program keys into inline encryption hardware. For more information on the Keyslot Manager, refer to documentation found inblock/keyslot-manager.candlinux/keyslot-manager.h.
Quoted 3 lines
Co-developed-by Eric Biggers <[email protected]>Signed-off-by Eric Biggers <[email protected]>Signed-off-by Satya Tangirala <[email protected]>
Thanks, this patch looks much better now. I don't see any real issues, but as usual here are a couple nits I noticed while reading through this latest version :-)
block/keyslot-manager.c line 74
Quoted 12 lines
block/keyslot-manager.c new file +12
-0+/** +* blk_ksm_init() - Initialize a keyslot manager +* @ksm: The keyslot_manager to initialize. +* @dev: Device for runtime power management (NULL if none) +* @num_slots: The number of key slots to manage. +* +* Allocate memory for keyslots and initialize a keyslot manager. Called by +* e.g. storage drivers to set up a keyslot manager in their request_queue. +* +* Return: 0 on success, or else a negative error code. +*/ +int blk_ksm_init (struct blk_keyslot_manager *ksm,unsigned int num_slots)
The @dev parameter was removed, so its kerneldoc should be too.
One tip, you can check the validity of kerneldoc comments by running:
$ ./scripts/kernel-doc -v -none block/keyslot-manager.c block/keyslot-manager.c:67: info: Scanning doc for blk_ksm_init block/keyslot-manager.c:78: warning: Excess function parameter 'dev' description in 'blk_ksm_init' block/keyslot-manager.c:180: info: Scanning doc for blk_ksm_get_slot_for_key block/keyslot-manager.c:198: warning: Function parameter or member 'slot_ptr' not described in 'blk_ksm_get_slot_for_key' block/keyslot-manager.c:198: warning: Excess function parameter 'keyslot' description in 'blk_ksm_get_slot_for_key' block/keyslot-manager.c:258: info: Scanning doc for blk_ksm_put_slot block/keyslot-manager.c:282: info: Scanning doc for blk_ksm_crypto_key_supported block/keyslot-manager.c:303: info: Scanning doc for blk_ksm_evict_key block/keyslot-manager.c:343: info: Scanning doc for blk_ksm_reprogram_all_keys 3 warnings
Quoted 8 lines
+/**
+ *blk_ksm_get_slot_for_key()- Program a key into a keyslot.
+ * @ksm: The keyslot manager to program the key into.
+ * @key: Pointer to the key object to program, including the raw key, crypto
+ * mode, and data unit size.
+ * @keyslot: A pointer to return the pointer of the allocated keyslot.
+ *
+ * Get a keyslot that's been programmed with the specified key. If one already
Quoted 8 lines
+ * exists, return it with incremented refcount. Otherwise, wait for a keyslot
+ * to become idle and program it.
+ *
+ * Context: Process context. Takes and releasesksm->lock.
+ * Return:BLK_STATUS_OKon success (and keyslot is set to the pointer of the
+ * allocated keyslot), or some otherblk_status_totherwise (and
+ * keyslot is set to NULL).
+ */
It's actually "BLK_STS_OK", not "BLK_STATUS_OK".
Quoted 13 lines
include/linux/blkdev.h +1
-0@@ -43,6 +43,7 @@ struct pr_ops;struct rq_qos ;struct blk_queue_stats ;struct blk_stat_callback ; +struct blk_keyslot_manager ;#define BLKDEV_MIN_RQ 4#define BLKDEV_MAX_RQ 128/* Default maximum */
include/linux/blkdev.h struct request_queue { · line 481
Quoted 7 lines
include/linux/blkdev.h +4
-0@@ -474,6 +475,11 @@ struct request_queue {unsigned int dma_pad_mask;unsigned int dma_alignment; +#ifdef CONFIG_BLK_INLINE_ENCRYPTION +/* Inline crypto capabilities */ +struct blk_keyslot_manager *ksm; +#endif
I do still wonder whether the concept of inline crypto support should be more separated from keyslot management, to be better prepared for device-mapper passthrough support and for hardware that accepts keys directly. (Such hardware exists, though I'm not sure support for it will be upstreamed.) For example, the crypto capabilities could be stored in a 'struct blk_crypto_capabilities' rather than in 'struct blk_keyslot_manager', and the latter could be optional.
What you have now is fine for the functionality in the current patchset though, so I'm not really complaining. Just something to think about.
- Eric
Re: [PATCH v9 01/11] block: Keyslot Manager for Inline Encryption
Quoted 12 lines · Eric Biggers
include/linux/blkdev.h struct request_queue { · line 481
Quoted 4 lines
include/linux/blkdev.h +4
-0+#ifdef CONFIG_BLK_INLINE_ENCRYPTION +/* Inline crypto capabilities */ +struct blk_keyslot_manager *ksm; +#endif I do still wonder whether the concept of inline crypto support should be more separated from keyslot management, to be better prepared for device-mapper passthrough support and for hardware that accepts keys directly. (Such hardware exists, though I'm not sure support for it will be upstreamed.) For example, the crypto capabilities could be stored in a 'struct
blk_crypto_capabilities' rather than in 'structblk_keyslot_manager', and the latter could be optional.
Quoted 2 lines
What you have now is fine for the functionality in the current patchset though, so I'm not really complaining. Just something to think about.
I'd rather keep things simple (aka as-is) for now. If needed we can change it. I doubt we'll even have a handful drivers with inline crypto in the next years..
PATCH v9 2/11 block: Inline encryption support for blk-mq
In reply to Satya TangiralaWe must have some way of letting a storage device driver know what encryption context it should use for en/decrypting a request. However, it's the upper layers (like the filesystem/fscrypt) that know about and manages encryption contexts. As such, when the upper layer submits a bio to the block layer, and this bio eventually reaches a device driver with support for inline encryption, the device driver will need to have been told the encryption context for that bio.
We want to communicate the encryption context from the upper layer to the storage device along with the bio, when the bio is submitted to the block layer. To do this, we add a struct bio_crypt_ctx to struct bio, which can represent an encryption context (note that we can't use the bi_private field in struct bio to do this because that field does not function to pass information across layers in the storage stack). We also introduce various functions to manipulate the bio_crypt_ctx and make the bio/request merging logic aware of the bio_crypt_ctx.
We also make changes to blk-mq to make it handle bios with encryption contexts. blk-mq can merge many bios into the same request. These bios need to have contiguous data unit numbers (the necessary changes to blk-merge are also made to ensure this) - as such, it suffices to keep the data unit number of just the first bio, since that's all a storage driver needs to infer the data unit number to use for each data block in each bio in a request. blk-mq keeps track of the encryption context to be used for all the bios in a request with the request's rq_crypt_ctx. When the first bio is added to an empty request, blk-mq will program the encryption context of that bio into the request_queue's keyslot manager, and store the returned keyslot in the request's rq_crypt_ctx. All the functions to operate on encryption contexts are in blk-crypto.c.
Upper layers only need to call bio_crypt_set_ctx with the encryption key, algorithm and data_unit_num; they don't have to worry about getting a keyslot for each encryption context, as blk-mq/blk-crypto handles that. Blk-crypto also makes it possible for request-based layered devices like dm-rq to make use of inline encryption hardware by cloning the rq_crypt_ctx and programming a keyslot in the new request_queue when necessary.
Note that any user of the block layer can submit bios with an encryption context, such as filesystems, device-mapper targets, etc.
--- block/Makefile | 2 +- block/bio.c | 6 + block/blk-core.c | 20 +- block/blk-crypto-internal.h | 172 ++++++++++++++++ block/blk-crypto.c | 388 ++++++++++++++++++++++++++++++++++++ block/blk-map.c | 1 + block/blk-merge.c | 11 + block/blk-mq.c | 12 ++ block/blk.h | 4 + block/bounce.c | 2 + drivers/md/dm.c | 3 + include/linux/blk-crypto.h | 71 ++++++- include/linux/blk_types.h | 6 + include/linux/blkdev.h | 5 + 14 files changed, 697 insertions(+), 6 deletions(-) create mode 100644 block/blk-crypto-internal.h create mode 100644 block/blk-crypto.c
block/Makefile +1 -1
@@ -37,4 +37,4 @@ obj-$(CONFIG_BLK_DEBUG_FS) += blk-mq-debugfs.o obj-$(CONFIG_BLK_DEBUG_FS_ZONED)+= blk-mq-debugfs-zoned.o obj-$(CONFIG_BLK_SED_OPAL) += sed-opal.o obj-$(CONFIG_BLK_PM) += blk-pm.o -obj-$(CONFIG_BLK_INLINE_ENCRYPTION) += keyslot-manager.o +obj-$(CONFIG_BLK_INLINE_ENCRYPTION) += keyslot-manager.o blk-crypto.o
block/bio.c +6 -0
@@ -17,6 +17,7 @@#include <linux/cgroup.h> #include <linux/blk-cgroup.h> #include <linux/highmem.h> +#include <linux/blk-crypto.h> #include <trace/events/block.h> #include "blk.h"
@@ -236,6 +237,8 @@ void bio_uninit(struct bio *bio)if (bio_integrity (bio))bio_integrity_free (bio); + +bio_crypt_free_ctx (bio); }EXPORT_SYMBOL (bio_uninit);
@@ -664,6 +667,8 @@ struct bio *bio_clone_fast(struct bio *bio, gfp_t gfp_mask, struct bio_set *bs)__bio_clone_fast (b, bio); +bio_crypt_clone (b, bio, gfp_mask); +if (bio_integrity (bio)) {int ret;
@@ -1046,6 +1051,7 @@ void bio_advance(struct bio *bio, unsigned bytes)if (bio_integrity (bio))bio_integrity_advance (bio, bytes); +bio_crypt_advance (bio, bytes);bio_advance_iter (bio, &bio->bi_iter, bytes); }EXPORT_SYMBOL (bio_advance);
block/blk-core.c +16 -4
@@ -38,6 +38,7 @@#include <linux/debugfs.h> #include <linux/bpf.h> #include <linux/psi.h> +#include <linux/blk-crypto.h> #define CREATE_TRACE_POINTS #include <trace/events/block.h>
@@ -120,6 +121,7 @@ void blk_rq_init(struct request_queue *q, struct request *rq) rq->start_time_ns =ktime_get_ns (); rq->part =NULL ;refcount_set (&rq->ref,1 ); +blk_crypto_rq_set_defaults (rq); }EXPORT_SYMBOL (blk_rq_init);
@@ -617,6 +619,8 @@ bool bio_attempt_back_merge(struct request *req, struct bio *bio, req->biotail = bio; req->__data_len += bio->bi_iter.bi_size; +bio_crypt_free_ctx (bio); +blk_account_io_start (req, false);return true; }
@@ -641,6 +645,8 @@ bool bio_attempt_front_merge(struct request *req, struct bio *bio, req->__sector = bio->bi_iter.bi_sector; req->__data_len += bio->bi_iter.bi_size; +blk_crypto_rq_bio_prep (req, bio); +blk_account_io_start (req, false);return true; }
@@ -1066,7 +1072,8 @@ blk_qc_t generic_make_request(struct bio *bio)/* Create a fresh bio_list for all subordinate requests */ bio_list_on_stack[1 ] = bio_list_on_stack[0 ];bio_list_init (&bio_list_on_stack[0 ]); - ret = q->make_request_fn (q, bio); +if (blk_crypto_bio_prep (&bio)) + ret = q->make_request_fn (q, bio);blk_queue_exit (q);
@@ -1114,7 +1121,7 @@ blk_qc_t direct_make_request(struct bio *bio) {struct request_queue *q = bio->bi_disk->queue;bool nowait = bio->bi_opf &REQ_NOWAIT ; -blk_qc_t ret; +blk_qc_t ret =BLK_QC_T_NONE ;if (!generic_make_request_checks (bio))return BLK_QC_T_NONE ;
@@ -1127,8 +1134,8 @@ blk_qc_t direct_make_request(struct bio *bio)bio_endio (bio);return BLK_QC_T_NONE ; } - - ret = q->make_request_fn (q, bio); +if (blk_crypto_bio_prep (&bio)) + ret = q->make_request_fn (q, bio);blk_queue_exit (q);return ret; }
@@ -1258,6 +1265,9 @@ blk_status_t blk_insert_cloned_request(struct request_queue *q, struct request * should_fail_request(&rq->rq_disk->part0, blk_rq_bytes(rq)))return BLK_STS_IOERR ; +if (blk_crypto_insert_cloned_request (rq)) +return BLK_STS_IOERR ; +if (blk_queue_io_stat (q))blk_account_io_start (rq, true);
@@ -1646,6 +1656,8 @@ int blk_rq_prep_clone(struct request *rq, struct request *rq_src,__blk_rq_prep_clone (rq, rq_src); +blk_crypto_rq_prep_clone (rq, rq_src); +return 0 ; free_and_out:
block/blk-crypto-internal.h new file +172 -0
172 lines not on this page · raw message
block/blk-crypto.c new file +388 -0
388 lines not on this page · raw message
block/blk-map.c +1 -0
@@ -41,6 +41,7 @@ int blk_rq_append_bio(struct request *rq, struct bio **bio) rq->biotail->bi_next = *bio; rq->biotail = *bio; rq->__data_len += (*bio)->bi_iter.bi_size; +bio_crypt_free_ctx (*bio); }return 0 ;
block/blk-merge.c +11 -0
@@ -596,6 +596,8 @@ int ll_back_merge_fn(struct request *req, struct bio *bio, unsigned int nr_segs)if (blk_integrity_rq (req) &&integrity_req_gap_back_merge (req, bio))return 0 ; +if (!bio_crypt_ctx_back_mergeable (req, bio)) +return 0 ;if (blk_rq_sectors (req) +bio_sectors (bio) >blk_rq_get_max_sectors (req,blk_rq_pos (req))) {req_set_nomerge (req->q, req);
@@ -612,6 +614,8 @@ int ll_front_merge_fn(struct request *req, struct bio *bio, unsigned int nr_segsif (blk_integrity_rq (req) &&integrity_req_gap_front_merge (req, bio))return 0 ; +if (!bio_crypt_ctx_front_mergeable (req, bio)) +return 0 ;if (blk_rq_sectors (req) +bio_sectors (bio) >blk_rq_get_max_sectors (req, bio->bi_iter.bi_sector)) {req_set_nomerge (req->q, req);
@@ -661,6 +665,9 @@ static int ll_merge_requests_fn(struct request_queue *q, struct request *req,if (blk_integrity_merge_rq (q, req, next) == false)return 0 ; +if (!bio_crypt_ctx_merge_rq (req, next)) +return 0 ; +/* Merge is OK... */ req->nr_phys_segments = total_phys_segments;return 1 ;
@@ -885,6 +892,10 @@ bool blk_rq_merge_ok(struct request *rq, struct bio *bio)if (blk_integrity_merge_bio (rq->q, rq, bio) == false)return false; +/* Only merge if the crypt contexts are compatible */ +if (!bio_crypt_rq_ctx_compatible (rq, bio)) +return false; +/* must be using the same buffer */ if (req_op (rq) ==REQ_OP_WRITE_SAME && !blk_write_same_mergeable (rq->bio, bio))
block/blk-mq.c +12 -0
@@ -26,6 +26,7 @@#include <linux/delay.h> #include <linux/crash_dump.h> #include <linux/prefetch.h> +#include <linux/blk-crypto.h> #include <trace/events/block.h>
@@ -317,6 +318,7 @@ static struct request *blk_mq_rq_ctx_init(struct blk_mq_alloc_data *data,#if defined(CONFIG_BLK_DEV_INTEGRITY ) rq->nr_integrity_segments =0 ;#endif +blk_crypto_rq_set_defaults (rq);/* tag was already set */ rq->extra_len =0 ;WRITE_ONCE (rq->deadline,0 );
@@ -474,6 +476,7 @@ static void __blk_mq_free_request(struct request *rq)struct blk_mq_hw_ctx *hctx = rq->mq_hctx;const int sched_tag = rq->internal_tag; +blk_crypto_free_request (rq);blk_pm_mark_last_busy (rq); rq->mq_hctx =NULL ;if (rq->tag !=-1 )
@@ -1971,6 +1974,7 @@ static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio)struct request *same_queue_rq =NULL ;unsigned int nr_segs;blk_qc_t cookie; +blk_status_t ret;blk_queue_bounce (q, &bio);__blk_queue_split (q, &bio, &nr_segs);
@@ -2002,6 +2006,14 @@ static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio) cookie =request_to_qc_t (data.hctx, rq); + ret =blk_crypto_init_request (rq,bio_crypt_key (bio)); +if (ret !=BLK_STS_OK ) { + bio->bi_status = ret; +bio_endio (bio); +blk_mq_free_request (rq); +return BLK_QC_T_NONE ; + } +blk_mq_bio_to_request (rq, bio, nr_segs); plug =blk_mq_plug (q, bio);
block/blk.h +4 -0
@@ -4,7 +4,9 @@#include <linux/idr.h> #include <linux/blk-mq.h> +#include <linux/blk-crypto.h> #include <xen/xen.h> +#include "blk-crypto-internal.h" #include "blk-mq.h" #include "blk-mq-sched.h"
@@ -117,6 +119,8 @@ static inline void blk_rq_bio_prep(struct request *rq, struct bio *bio,if (bio->bi_disk) rq->rq_disk = bio->bi_disk; + +blk_crypto_rq_bio_prep (rq, bio); }#ifdef CONFIG_BLK_DEV_INTEGRITY
block/bounce.c +2 -0
@@ -267,6 +267,8 @@ static struct bio *bounce_clone_bio(struct bio *bio_src, gfp_t gfp_mask,break ; } +bio_crypt_clone (bio, bio_src, gfp_mask); +if (bio_integrity (bio_src)) {int ret;
drivers/md/dm.c +3 -0
@@ -25,6 +25,7 @@#include <linux/wait.h> #include <linux/pr.h> #include <linux/refcount.h> +#include <linux/blk-crypto.h> #define DM_MSG_PREFIX "core"
@@ -1304,6 +1305,8 @@ static int clone_bio(struct dm_target_io *tio, struct bio *bio,__bio_clone_fast (clone, bio); +bio_crypt_clone (clone, bio,GFP_NOIO ); +if (bio_integrity (bio)) {int r;
include/linux/blk-crypto.h +70 -1
87 lines not on this page · raw message
include/linux/blk_types.h +6 -0
@@ -18,6 +18,7 @@ struct block_device;struct io_context ;struct cgroup_subsys_state ;typedef void (bio_end_io_t ) (struct bio *); +struct bio_crypt_ctx ;/* * Block error status values. See block/blk-core:blk_errors for the details.
@@ -173,6 +174,11 @@ struct bio {u64 bi_iocost_cost;#endif #endif + +#ifdef CONFIG_BLK_INLINE_ENCRYPTION +struct bio_crypt_ctx *bi_crypt_context; +#endif +union {#if defined(CONFIG_BLK_DEV_INTEGRITY )struct bio_integrity_payload *bi_integrity;/* data integrity */
include/linux/blkdev.h +5 -0
@@ -224,6 +224,11 @@ struct request {unsigned short nr_integrity_segments;#endif +#ifdef CONFIG_BLK_INLINE_ENCRYPTION +struct bio_crypt_ctx *crypt_ctx; +struct blk_ksm_keyslot *crypt_keyslot; +#endif +unsigned short write_hint;unsigned short ioprio;
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerRe: [PATCH v9 02/11] block: Inline encryption support for blk-mq
Quoted 10 lines · Satya Tangirala
block/blk-crypto-internal.h new file +4
-0@@ -0,0 +1,172 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* Copyright 2019 Google LLC +*/
block/blk-crypto-internal.h line 14
Quoted 10 lines
block/blk-crypto-internal.h new file +10
-0+ +#ifndef __LINUX_BLK_CRYPTO_INTERNAL_H +#define __LINUX_BLK_CRYPTO_INTERNAL_H + +#include <linux/bio.h> +#include <linux/blkdev.h> + +/* Represents a crypto mode supported by blk-crypto */ +struct blk_crypto_mode { + const char *cipher_str; /* crypto API name (for fallback case) */
Technically, cipher_str shouldn't be added until the patch that adds blk-crypto-fallback.
block/blk-crypto-internal.h line 26
Quoted 12 lines
block/blk-crypto-internal.h new file +12
-0+unsigned int keysize;/* key size in bytes */ +unsigned int ivsize;/* iv size in bytes */ +}; + +#ifdef CONFIG_BLK_INLINE_ENCRYPTION + +static inline const struct blk_crypto_key *bio_crypt_key (struct bio *bio) +{ +if (!bio_has_crypt_ctx (bio)) +return NULL ; +return bio->bi_crypt_context->bc_key; +}
I don't believe bio_crypt_key() is necessary -- see my comment below regarding blk_mq_make_request().
block/blk-crypto-internal.h line 29
Quoted 3 lines
block/blk-crypto-internal.h new file +3
-0+bool bio_crypt_dun_is_contiguous (const struct bio_crypt_ctx *bc, +unsigned int bytes, +u64 next_dun[BLK_CRYPTO_DUN_ARRAY_SIZE ])
next_dun should be const.
Quoted 8 lines
block/blk-crypto-internal.h new file +8
-0+{ +int i =0 ; +unsigned int inc = bytes >> bc->bc_key->data_unit_size_bits; + +while (i <BLK_CRYPTO_DUN_ARRAY_SIZE ) { +if (bc->bc_dun[i] + inc != next_dun[i]) +return false; +/*
block/blk-crypto-internal.h line 47
Quoted 10 lines
block/blk-crypto-internal.h new file +10
-0+* If addition of inc to the current entry caused an overflow, +* then we have to carry "1" for the next entry - so inc +* needs to be "1" for the next loop iteration). Otherwise, +* we need inc to be 0 for the next loop iteration. Since +* overflow can be determined by (bc->bc_dun[i] + inc) < inc +* we can do the following. +*/ + inc = ((bc->bc_dun[i] + inc) < inc); + i++; + }
This comment is verbose but doesn't really explain what's going on. I think it would be much more useful to add comments like:
/*
* Returns true if @bc_dun plus @bytes converted to data units is equal to
* @next_dun, treating the DUNs as multi-limb integers.
*/
bool bio_crypt_dun_is_contiguous(const struct bio_crypt_ctx *bc,
unsigned int bytes,
const u64 next_dun[BLK_CRYPTO_DUN_ARRAY_SIZE])
And:
/* * If the addition in this limb overflowed, then the carry bit * into the next limb is 1. Else the carry bit is 0. */ inc = ((bc->bc_dun[i] + inc) < inc);
block/blk-crypto-internal.h line 54
Quoted 7 lines
block/blk-crypto-internal.h new file +7
-0+ +/* +* After going through all the entries in the dun, inc must be 0 for +* the duns to be contiguous. +*/ +return !inc; +}
This is new in v9; before it just returned true.
It would be more helpful if this comment was like:
/* If the DUN wrapped through 0, don't treat it as contiguous. */
Quoted 9 lines
block/blk-crypto-internal.h new file +9
-0+/** +* __blk_crypto_init_request - Initializes the request's crypto fields based on +* the blk_crypto_key for a bio to be added to the +* request, and prepares it for hardware inline +* encryption. +* +* @rq: The request to init +* @key: The blk_crypto_key of bios that will (eventually) be added to @rq. +*
block/blk-crypto-internal.h line 73
Quoted 10 lines
block/blk-crypto-internal.h new file +10
-0+* Initializes the request's crypto fields to appropriate default values and +* tries to get a keyslot for the blk_crypto_key. +* +* Return: BLK_STATUS_OK on success, and negative error code otherwise. +*/ +blk_status_t __blk_crypto_init_request (struct request *rq, +const struct blk_crypto_key *key) +{ +return blk_ksm_get_slot_for_key (rq->q->ksm, key, &rq->crypt_keyslot); +}
The comment of this function seems outdated. All it does it get a keyslot, but the comment talks about initializing "crypto fields" (plural).
Quoted 12 lines
block/blk-crypto-internal.h new file +12
-0+/** +* blk_crypto_evict_key() - Evict a key from any inline encryption hardware +* it may have been programmed into +* @q: The request queue who's keyslot manager this key might have been +* programmed into +* @key: The key to evict +* +* Upper layers (filesystems) should call this function to ensure that a key +* is evicted from hardware that it might have been programmed into. This +* will call blk_ksm_evict_key on the queue's keyslot manager, if one +* exists, and supports the crypto algorithm with the specified data unit size. +*
block/blk-crypto-internal.h line 95
Quoted 10 lines
block/blk-crypto-internal.h new file +10
-0+* Return: 0 on success or if key is not present in the q's ksm, -err on error. +*/ +int blk_crypto_evict_key (struct request_queue *q, +const struct blk_crypto_key *key) +{ +if (q->ksm &&blk_ksm_crypto_key_supported (q->ksm, key)) +return blk_ksm_evict_key (q->ksm, key); + +return 0 ; +}
The keyslot manager is really an implementation detail of the block layer. Therefore when documenting functions like blk_crypto_evict_key() that are the API for use by upper layers like filesystems, we shouldn't really talk about the keyslot manager, but rather describe the behavior in higher-level terms like "evict a key from the inline encryption hardware".
Quoted 11 lines
block/blk-crypto-internal.h new file +1
-0@@ -1971,6 +1974,7 @@ static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio)struct request *same_queue_rq =NULL ;unsigned int nr_segs;blk_qc_t cookie; +blk_status_t ret;blk_queue_bounce (q, &bio);__blk_queue_split (q, &bio, &nr_segs);@@ -2002,6 +2006,14 @@ static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio) cookie =request_to_qc_t (data.hctx, rq);
block/blk-crypto-internal.h static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio) · line 2017
Quoted 10 lines
block/blk-crypto-internal.h new file +8
-0+ ret =blk_crypto_init_request (rq,bio_crypt_key (bio)); +if (ret !=BLK_STS_OK ) { + bio->bi_status = ret; +bio_endio (bio); +blk_mq_free_request (rq); +return BLK_QC_T_NONE ; + } +blk_mq_bio_to_request (rq, bio, nr_segs);
Wouldn't it make a lot more sense to do blk_crypto_init_request() after blk_mq_bio_to_request() rather than before?
I.e., initialize request::crypt_ctx first, *then* get the keyslot. Not the other way around.
That would allow removing the second argument to blk_crypto_init_request() and removing bio_crypt_key(). blk_crypto_init_request() would only need to take in the struct request.
Quoted 14 lines
include/linux/blk-crypto.h +2
-0@@ -6,6 +6,8 @@#ifndef __LINUX_BLK_CRYPTO_H#define __LINUX_BLK_CRYPTO_H +#include <linux/types.h> +enum blk_crypto_mode_num {BLK_ENCRYPTION_MODE_INVALID , BLK_ENCRYPTION_MODE_AES_256_XTS,
include/linux/blk-crypto.h enum blk_crypto_mode_num { · line 29
Quoted 5 lines
include/linux/blk-crypto.h +1
-1@@ -24,7 +26,7 @@ enum blk_crypto_mode_num {* ciphertext. This is always a power of 2. It might be e.g. the * filesystem block size or the disk sector size. * @data_unit_size_bits: log2 of data_unit_size -* @dun_bytes: the number of bytes of DUN used when using this key +* @dun_bytes: the maximum number of bytes of DUN used when using this key
This comment update should be folded into the patch that added this.
Quoted 7 lines
include/linux/blk-crypto.h +7
-0+/** +* struct bio_crypt_ctx - an inline encryption context +* @bc_key: the key, algorithm, and data unit size to use +* @bc_dun: the data unit number (starting IV) to use +* @bc_keyslot: the keyslot that has been assigned for this key in @bc_ksm, +* or -1 if no keyslot has been assigned yet. +* @bc_ksm: the keyslot manager into which the key has been programmed with
include/linux/blk-crypto.h struct blk_crypto_key { · line 66
Quoted 10 lines
include/linux/blk-crypto.h +10
-0+* @bc_keyslot, or NULL if this key hasn't yet been programmed. +* +* A bio_crypt_ctx specifies that the contents of the bio will be encrypted (for +* write requests) or decrypted (for read requests) inline by the storage device +* or controller. +*/ +struct bio_crypt_ctx { +const struct blk_crypto_key *bc_key; +u64 bc_dun[BLK_CRYPTO_DUN_ARRAY_SIZE ]; +};
Kerneldoc needs to be updated; bc_keyslot and bc_ksm no longer exist.
- Eric
Re: [PATCH v9 02/11] block: Inline encryption support for blk-mq
Quoted 13 lines · Eric Biggers
Quoted 13 lines
block/blk-crypto.c new file +13
-0+{ +int i =0 ; +unsigned int inc = bytes >> bc->bc_key->data_unit_size_bits; + +while (i <BLK_CRYPTO_DUN_ARRAY_SIZE ) { +if (bc->bc_dun[i] + inc != next_dun[i]) +return false; +/* +* If addition of inc to the current entry caused an overflow, +* then we have to carry "1" for the next entry - so inc +* needs to be "1" for the next loop iteration). Otherwise, +* we need inc to be 0 for the next loop iteration. Since +* overflow can be determined by (bc->bc_dun[i] + inc) < inc
Quoted 8 lines
block/blk-crypto.c line 143
Quoted 5 lines
block/blk-crypto.c new file +5
-0+* we can do the following. +*/ + inc = ((bc->bc_dun[i] + inc) < inc); + i++; + }This comment is verbose but doesn't really explain what's going on. I think it would be much more useful to add comments like:
Also the code is still weird. Odd double whitespaces, expression that evaluate to bool.
Quoted 6 lines
/* * If the addition in this limb overflowed, then the carry bit * into the next limb is 1. Else the carry bit is 0. */ inc = ((bc->bc_dun[i] + inc) < inc);
if (bc->bc_dun[i] + carry < carry) carry = 1; else carry = 0;
Quoted 9 lines
block/blk-crypto.c line 223
Quoted 6 lines
block/blk-crypto.c new file +5
-0+blk_status_t __blk_crypto_init_request (struct request *rq, +const struct blk_crypto_key *key) +{ +return blk_ksm_get_slot_for_key (rq->q->ksm, key, &rq->crypt_keyslot); +}The comment of this function seems outdated. All it does it get a keyslot, but the comment talks about initializing "crypto fields" (plural).
This is a classic case where I think the top of the function comment is entirely useless. If there is a single caller in core code and the function is completely trivial, there really is no point in a multi-line comment. Comment should explain something unexpected or non-trivial, while much of the comments in this series are just boilerplate making the code harder to read.
Quoted 19 lines
Quoted 5 lines
block/blk-mq.c +0
-0blk_queue_bounce (q, &bio);__blk_queue_split (q, &bio, &nr_segs);@@ -2002,6 +2006,14 @@ static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio) cookie =request_to_qc_t (data.hctx, rq);block/blk-mq.c static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio) · line 2017
Quoted 10 lines
block/blk-mq.c +8
-0+ ret =blk_crypto_init_request (rq,bio_crypt_key (bio)); +if (ret !=BLK_STS_OK ) { + bio->bi_status = ret; +bio_endio (bio); +blk_mq_free_request (rq); +return BLK_QC_T_NONE ; + } +blk_mq_bio_to_request (rq, bio, nr_segs);Wouldn't it make a lot more sense to do
blk_crypto_init_request()afterblk_mq_bio_to_request()rather than before?
Quoted 6 lines
I.e., initialize
request::crypt_ctxfirst, *then* get the keyslot. Not the other way around.That would allow removing the second argument to
blk_crypto_init_request()and removingbio_crypt_key().blk_crypto_init_request()would only need to take in the struct request.
And we can fail just the request on an error, so yes this doesn't seem too bad.
PATCH v9 3/11 block: Make blk-integrity preclude hardware inline encryption
In reply to Satya TangiralaWhenever a device supports blk-integrity, the kernel will now always pretend that the device doesn't support inline encryption (essentially by setting the keyslot manager in the request queue to NULL).
There's no hardware currently that supports both integrity and inline encryption. However, it seems possible that there will be such hardware in the near future (like the NVMe key per I/O support that might support both inline encryption and PI).
But properly integrating both features is not trivial, and without real hardware that implements both, it is difficult to tell if it will be done correctly by the majority of hardware that support both. So it seems best not to support both features together right now, and to decide what to do at probe time.
--- block/bio-integrity.c | 3 +++ block/blk-integrity.c | 7 +++++++ block/keyslot-manager.c | 19 +++++++++++++++++++ include/linux/blkdev.h | 30 ++++++++++++++++++++++++++++++ 4 files changed, 59 insertions(+)
block/bio-integrity.c +3 -0
@@ -42,6 +42,9 @@ struct bio_integrity_payload *bio_integrity_alloc(struct bio *bio,struct bio_set *bs = bio->bi_pool;unsigned inline_vecs; +if (WARN_ON_ONCE (bio_has_crypt_ctx (bio))) +return ERR_PTR (-EOPNOTSUPP ); +if (!bs || !mempool_initialized (&bs->bio_integrity_pool)) { bip =kmalloc (struct_size (bip, bip_inline_vecs, nr_vecs), gfp_mask); inline_vecs = nr_vecs;
block/blk-integrity.c +7 -0
@@ -409,6 +409,13 @@ void blk_integrity_register(struct gendisk *disk, struct blk_integrity *template bi->tag_size = template->tag_size; disk->queue->backing_dev_info->capabilities |=BDI_CAP_STABLE_WRITES ; + +#ifdef CONFIG_BLK_INLINE_ENCRYPTION +if (disk->queue->ksm) { +pr_warn ("blk-integrity: Integrity and hardware inline encryption are not supported together. Unregistering keyslot manager from request queue, to disable hardware inline encryption.\n" ); +blk_ksm_unregister (disk->queue); + } +#endif }EXPORT_SYMBOL (blk_integrity_register);
block/keyslot-manager.c +19 -0
@@ -25,6 +25,9 @@* Upper layers will call blk_ksm_get_slot_for_key() to program a * key into some slot in the inline encryption hardware. */ + +#define pr_fmt (fmt) "blk_crypto: " fmt +#include <crypto/algapi.h> #include <linux/keyslot-manager.h> #include <linux/atomic.h>
@@ -375,3 +378,19 @@ void blk_ksm_destroy(struct blk_keyslot_manager *ksm)memzero_explicit (ksm,sizeof (*ksm)); }EXPORT_SYMBOL_GPL (blk_ksm_destroy); + +bool blk_ksm_register (struct blk_keyslot_manager *ksm,struct request_queue *q) +{ +if (blk_integrity_queue_supports_integrity (q)) { +pr_warn ("Integrity and hardware inline encryption are not supported together. Hardware inline encryption is being disabled.\n" ); +return false; + } + q->ksm = ksm; +return true; +} +EXPORT_SYMBOL_GPL (blk_ksm_register); + +void blk_ksm_unregister (struct request_queue *q) +{ + q->ksm =NULL ; +}
include/linux/blkdev.h +30 -0
@@ -1569,6 +1569,12 @@ struct blk_integrity *bdev_get_integrity(struct block_device *bdev)return blk_get_integrity (bdev->bd_disk); } +static inline bool +blk_integrity_queue_supports_integrity (struct request_queue *q) +{ +return q->integrity.profile; +} +static inline bool blk_integrity_rq (struct request *rq) {return rq->cmd_flags &REQ_INTEGRITY ;
@@ -1649,6 +1655,11 @@ static inline struct blk_integrity *blk_get_integrity(struct gendisk *disk) {return NULL ; } +static inline bool +blk_integrity_queue_supports_integrity (struct request_queue *q) +{ +return false; +}static inline int blk_integrity_compare (struct gendisk *a,struct gendisk *b) {return 0 ;
@@ -1700,6 +1711,25 @@ static inline struct bio_vec *rq_integrity_vec(struct request *rq)#endif /* CONFIG_BLK_DEV_INTEGRITY */ +#ifdef CONFIG_BLK_INLINE_ENCRYPTION + +bool blk_ksm_register (struct blk_keyslot_manager *ksm,struct request_queue *q); + +void blk_ksm_unregister (struct request_queue *q); + +#else /* CONFIG_BLK_INLINE_ENCRYPTION */ + +static inline bool blk_ksm_register (struct blk_keyslot_manager *ksm, +struct request_queue *q) +{ +return true; +} + +static inline void blk_ksm_unregister (struct request_queue *q) { } + +#endif /* CONFIG_BLK_INLINE_ENCRYPTION */ + +struct block_device_operations {int (*open) (struct block_device *,fmode_t );void (*release) (struct gendisk *,fmode_t );
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
PATCH v9 4/11 block: blk-crypto-fallback for Inline Encryption
In reply to Satya TangiralaBlk-crypto delegates crypto operations to inline encryption hardware when available. The separately configurable blk-crypto-fallback contains a software fallback to the kernel crypto API - when enabled, blk-crypto will use this fallback for en/decryption when inline encryption hardware is not available. This lets upper layers not have to worry about whether or not the underlying device has support for inline encryption before deciding to specify an encryption context for a bio, and also allows for testing without actual inline encryption hardware. For more details, refer to Documentation/block/inline-encryption.rst.
--- Documentation/block/index.rst | 1 + Documentation/block/inline-encryption.rst | 195 +++++++ block/Kconfig | 10 + block/Makefile | 1 + block/blk-crypto-fallback.c | 666 ++++++++++++++++++++++ block/blk-crypto-internal.h | 25 + block/blk-crypto.c | 46 +- include/linux/blk-crypto.h | 17 +- 8 files changed, 947 insertions(+), 14 deletions(-) create mode 100644 Documentation/block/inline-encryption.rst create mode 100644 block/blk-crypto-fallback.c
Documentation/block/index.rst +1 -0
@@ -14,6 +14,7 @@ Block cmdline-partition data-integrity deadline-iosched + inline-encryption ioprio kyber-iosched null_blk
Documentation/block/inline-encryption.rst new file +195 -0
195 lines not on this page · raw message
block/Kconfig +10 -0
@@ -192,6 +192,16 @@ config BLK_INLINE_ENCRYPTION block layer handle encryption, so users can take advantage of inline encryption hardware if present. +config BLK_INLINE_ENCRYPTION_FALLBACK + bool "Enable crypto API fallback for blk-crypto" + depends on BLK_INLINE_ENCRYPTION + select CRYPTO + select CRYPTO_SKCIPHER + help + Enabling this lets the block layer handle inline encryption + by falling back to the kernel crypto API when inline + encryption hardware is not present. + menu "Partition Types" source "block/partitions/Kconfig"
block/Makefile +1 -0
@@ -38,3 +38,4 @@ obj-$(CONFIG_BLK_DEBUG_FS_ZONED)+= blk-mq-debugfs-zoned.o obj-$(CONFIG_BLK_SED_OPAL) += sed-opal.o obj-$(CONFIG_BLK_PM) += blk-pm.o obj-$(CONFIG_BLK_INLINE_ENCRYPTION) += keyslot-manager.o blk-crypto.o +obj-$(CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK) += blk-crypto-fallback.o
block/blk-crypto-fallback.c new file +666 -0
666 lines not on this page · raw message
block/blk-crypto-internal.h +25 -0
@@ -16,6 +16,8 @@ struct blk_crypto_mode {unsigned int ivsize;/* iv size in bytes */ }; +extern const struct blk_crypto_mode blk_crypto_modes[]; +#ifdef CONFIG_BLK_INLINE_ENCRYPTION static inline const struct blk_crypto_key *bio_crypt_key (struct bio *bio)
@@ -169,4 +171,27 @@ static inline blk_status_t blk_crypto_insert_cloned_request(struct request *rq) return BLK_STS_OK; } +#ifdef CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK + +bool blk_crypto_fallback_bio_prep (struct bio **bio_ptr); + +int blk_crypto_fallback_evict_key (const struct blk_crypto_key *key); + +#else /* CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK */ + +static inline bool blk_crypto_fallback_bio_prep (struct bio **bio_ptr) +{ +pr_warn_once ("crypto API fallback disabled; failing request.\n" ); + (*bio_ptr)->bi_status =BLK_STS_NOTSUPP ; +return false; +} + +static inline int +blk_crypto_fallback_evict_key (const struct blk_crypto_key *key) +{ +return 0 ; +} + +#endif /* CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK */ +#endif /* __LINUX_BLK_CRYPTO_INTERNAL_H */
block/blk-crypto.c +33 -13
94 lines not on this page · raw message
include/linux/blk-crypto.h +16 -1
@@ -58,7 +58,7 @@ struct blk_crypto_key {* * A bio_crypt_ctx specifies that the contents of the bio will be encrypted (for * write requests) or decrypted (for read requests) inline by the storage device -* or controller. +* or controller, or by the crypto API fallback. */ struct bio_crypt_ctx {const struct blk_crypto_key *bc_key;
@@ -111,4 +111,19 @@ static inline void bio_crypt_clone(struct bio *dst, struct bio *src, __bio_crypt_clone(dst, src, gfp_mask); } +#ifdef CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK + +int blk_crypto_start_using_key (struct blk_crypto_key *key, +struct request_queue *q); + +#else /* CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK */ + +static inline int blk_crypto_start_using_key (struct blk_crypto_key *key, +struct request_queue *q) +{ +return 0 ; +} + +#endif /* CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK */ +#endif /* __LINUX_BLK_CRYPTO_H */
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerRe: [PATCH v9 04/11] block: blk-crypto-fallback for Inline Encryption
Quoted 11 lines · Satya Tangirala
Blk-crypto delegates crypto operations to inline encryption hardware when available. The separately configurable blk-crypto-fallback contains a software fallback to the kernel crypto API - when enabled, blk-crypto will use this fallback for en/decryption when inline encryption hardware is not available. This lets upper layers not have to worry about whether or not the underlying device has support for inline encryption before deciding to specify an encryption context for a bio, and also allows for testing without actual inline encryption hardware. For more details, refer to
Documentation/block/inline-encryption.rst.Signed-off-by Satya Tangirala <[email protected]>
It might be helpful to also mention some real-world examples of how this helps testing, e.g. it makes it possible to test the inline encryption code in ext4 and f2fs simply by running xfstests with the inlinecrypt mount option. Therefore it makes it possible for the regular upstream regression testing of ext4 to cover the inline encryption code paths.
Documentation/block/inline-encryption.rst line 5
Quoted 11 lines
Documentation/block/inline-encryption.rst new file +5
-0@@ -0,0 +1,195 @@ +.. SPDX-License-Identifier: GPL-2.0 + +================= +Inline Encryption +=================
You may want to consider further improving this documentation file and then putting it as patch 1 of the series as its own patch to introduce the rest of the series, rather than "hiding" it in this particular patch. The documentation is for blk-crypto as a whole; it's not specific to blk-crypto-fallback.
Quoted 11 lines
Documentation/block/inline-encryption.rst new file +11
-0+struct bio_fallback_crypt_ctx { + struct bio_crypt_ctx crypt_ctx; + /* + * Copy of the bvec_iter when this bio was submitted. + * We only want to en/decrypt the part of the bio as described by the + * bvec_iter upon submission because bio might be split before being + * resubmitted + */ + struct bvec_iter crypt_iter; + u64 fallback_dun[BLK_CRYPTO_DUN_ARRAY_SIZE]; + union {
Documentation/block/inline-encryption.rst line 26
Quoted 10 lines
Documentation/block/inline-encryption.rst new file +10
-0+ struct { + struct work_struct work; + struct bio *bio; + }; + struct { + void *bi_private_orig; + bio_end_io_t *bi_end_io_orig; + }; + }; +};
Isn't 'fallback_dun' unnecessary now that blk-crypto-fallback uses bi_private? 'fallback_dun' should always be equal to 'crypt_ctx.bc_dun', right?
Documentation/block/inline-encryption.rst line 34
Quoted 8 lines
Documentation/block/inline-encryption.rst new file +8
-0+/** + * blk_crypto_fallback_bio_prep - Prepare a bio to use fallback en/decryption + * + * @bio_ptr: pointer to the bio to prepare + * + * If bio is doing a WRITE operation, we split the bio into two parts, resubmit + * the second part. Allocates a bounce bio for the first part, encrypts it, and + * update bio_ptr to point to the bounce bio.
This comment is misleading. The code actually only splits the bio if it's very large; it doesn't always split it.
Quoted 26 lines
block/blk-crypto.c +6
-1@@ -3,6 +3,10 @@* Copyright 2019 Google LLC */ +/* +* Refer to Documentation/block/inline-encryption.rst for detailed explanation. +*/ +#define pr_fmt (fmt) "blk-crypto: " fmt#include <linux/bio.h> @@ -206,7 +210,8 @@ static bool bio_crypt_check_alignment(struct bio *bio)* __blk_crypto_init_request - Initializes the request's crypto fields based on * the blk_crypto_key for a bio to be added to the * request, and prepares it for hardware inline -* encryption. +* encryption (as opposed to using the crypto API +* fallback). * * @rq: The request to init * @key: The blk_crypto_key of bios that will (eventually) be added to @rq.
block/blk-crypto.c static bool bio_crypt_check_alignment(struct bio *bio) · line 232
Quoted 9 lines
block/blk-crypto.c +4
-0@@ -219,6 +224,10 @@ static bool bio_crypt_check_alignment(struct bio *bio)blk_status_t __blk_crypto_init_request (struct request *rq,const struct blk_crypto_key *key) { +/* +* We have a bio crypt context here - that means we didn't fallback +* to crypto API, so try to program a keyslot now. +*/ return blk_ksm_get_slot_for_key (rq->q->ksm, key, &rq->crypt_keyslot); }
Since the fallback is now transparent to everything below it, we probably shouldn't leave as many comments like this around that mention the fallback. Comments are more useful if the code is doing something unexpected, as opposed to something expected.
block/blk-crypto.c void __blk_crypto_rq_bio_prep(struct request *rq, struct bio *bio) · line 321
Quoted 8 lines
block/blk-crypto.c +0
-0void __blk_crypto_rq_prep_clone (struct request *dst,struct request *src){
block/blk-crypto.c +4
-0+/* Don't clone crypto info if src uses fallback en/decryption */ +if (!src->crypt_keyslot) +return ; + dst->crypt_ctx = src->crypt_ctx; }
Isn't this part unnecessary? If the fallback was used, there is no crypt context anymore.
- Eric
PATCH v9 5/11 scsi: ufs: UFS driver v2.1 spec crypto additions
In reply to Satya TangiralaAdd the crypto registers and structs defined in v2.1 of the JEDEC UFSHCI specification in preparation to add support for inline encryption to UFS.
--- drivers/scsi/ufs/ufshcd.c | 2 ++ drivers/scsi/ufs/ufshcd.h | 5 +++ drivers/scsi/ufs/ufshci.h | 67 +++++++++++++++++++++++++++++++++++++-- 3 files changed, 72 insertions(+), 2 deletions(-)
drivers/scsi/ufs/ufshcd.c +2 -0
@@ -4766,6 +4766,8 @@ ufshcd_transfer_rsp_status(struct ufs_hba *hba, struct ufshcd_lrb *lrbp)case OCS_MISMATCH_RESP_UPIU_SIZE :case OCS_PEER_COMM_FAILURE :case OCS_FATAL_ERROR : +case OCS_INVALID_CRYPTO_CONFIG : +case OCS_GENERAL_CRYPTO_ERROR :default : result |=DID_ERROR <<16 ; dev_err(hba->dev,
drivers/scsi/ufs/ufshcd.h +5 -0
@@ -716,6 +716,11 @@ struct ufs_hba {* for userspace to control the power management. */ #define UFSHCD_CAP_RPM_AUTOSUSPEND (1 << 6) +/* +* This capability allows the host controller driver to use the +* inline crypto engine, if it is present +*/ +#define UFSHCD_CAP_CRYPTO (1 << 7)struct devfreq *devfreq;struct ufs_clk_scaling clk_scaling;
drivers/scsi/ufs/ufshci.h +65 -2
106 lines not on this page · raw message
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
PATCH v9 6/11 scsi: ufs: UFS crypto API
In reply to Satya TangiralaIntroduce functions to manipulate UFS inline encryption hardware in line with the JEDEC UFSHCI v2.1 specification and to work with the block keyslot manager.
The UFS crypto API will assume by default that a vendor driver doesn't support UFS crypto, even if the hardware advertises the capability, because a lot of hardware requires some special handling that's not specified in the aforementioned JEDEC spec. Each vendor driver must explicity set hba->caps |= UFSHCD_CAP_CRYPTO before ufshcd_hba_init_crypto is called to opt-in to UFS crypto support.
--- drivers/scsi/ufs/Kconfig | 9 ++ drivers/scsi/ufs/Makefile | 1 + drivers/scsi/ufs/ufshcd-crypto.c | 226 +++++++++++++++++++++++++++++++ drivers/scsi/ufs/ufshcd-crypto.h | 44 ++++++ drivers/scsi/ufs/ufshcd.h | 12 ++ 5 files changed, 292 insertions(+) create mode 100644 drivers/scsi/ufs/ufshcd-crypto.c create mode 100644 drivers/scsi/ufs/ufshcd-crypto.h
drivers/scsi/ufs/Kconfig +9 -0
@@ -160,3 +160,12 @@ config SCSI_UFS_BSG Select this if you need a bsg device node for your UFS controller. If unsure, say N. + +config SCSI_UFS_CRYPTO + bool "UFS Crypto Engine Support" + depends on SCSI_UFSHCD && BLK_INLINE_ENCRYPTION + help + Enable Crypto Engine Support in UFS. + Enabling this makes it possible for the kernel to use the crypto + capabilities of the UFS device (if present) to perform crypto + operations on data being transferred to/from the device.
drivers/scsi/ufs/Makefile +1 -0
@@ -7,6 +7,7 @@ obj-$(CONFIG_SCSI_UFS_QCOM) += ufs-qcom.o obj-$(CONFIG_SCSI_UFSHCD) += ufshcd-core.o ufshcd-core-y += ufshcd.o ufs-sysfs.o ufshcd-core-$(CONFIG_SCSI_UFS_BSG) += ufs_bsg.o +ufshcd-core-$(CONFIG_SCSI_UFS_CRYPTO) += ufshcd-crypto.o obj-$(CONFIG_SCSI_UFSHCD_PCI) += ufshcd-pci.o obj-$(CONFIG_SCSI_UFSHCD_PLATFORM) += ufshcd-pltfrm.o obj-$(CONFIG_SCSI_UFS_HISI) += ufs-hisi.o
drivers/scsi/ufs/ufshcd-crypto.c new file +226 -0
226 lines not on this page · raw message
drivers/scsi/ufs/ufshcd-crypto.h new file +44 -0
44 lines not on this page · raw message
drivers/scsi/ufs/ufshcd.h +12 -0
@@ -55,6 +55,7 @@#include <linux/clk.h> #include <linux/completion.h> #include <linux/regulator/consumer.h> +#include <linux/keyslot-manager.h> #include "unipro.h" #include <asm/irq.h>
@@ -521,6 +522,10 @@ struct ufs_stats {* @is_urgent_bkops_lvl_checked: keeps track if the urgent bkops level for * device is known or not. * @scsi_block_reqs_cnt: reference counting for scsi block requests +* @crypto_capabilities: Content of crypto capabilities register (0x100) +* @crypto_cap_array: Array of crypto capabilities +* @crypto_cfg_register: Start of the crypto cfg array +* @ksm: the keyslot manager tied to this hba */ struct ufs_hba {void __iomem *mmio_base;
@@ -735,6 +740,13 @@ struct ufs_hba {struct device bsg_dev;struct request_queue *bsg_queue; + +#ifdef CONFIG_SCSI_UFS_CRYPTO +union ufs_crypto_capabilities crypto_capabilities; +union ufs_crypto_cap_entry *crypto_cap_array; +u32 crypto_cfg_register; +struct blk_keyslot_manager ksm; +#endif };/* Returns true if clocks can be gated. Otherwise false */
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerRe: [PATCH v9 06/11] scsi: ufs: UFS crypto API
Quoted 11 lines · Satya Tangirala
Introduce functions to manipulate UFS inline encryption hardware in line with the JEDEC UFSHCI v2.1 specification and to work with the block keyslot manager.
The UFS crypto API will assume by default that a vendor driver doesn't support UFS crypto, even if the hardware advertises the capability, because a lot of hardware requires some special handling that's not specified in the aforementioned JEDEC spec. Each vendor driver must explicity set
hba->caps|=UFSHCD_CAP_CRYPTObeforeufshcd_hba_init_cryptois called to opt-in to UFS crypto support.
Thanks, this looks much better now!
A couple minor nits I noticed while reading this latest version:
drivers/scsi/ufs/ufshcd-crypto.c line 221
Quoted 6 lines
drivers/scsi/ufs/ufshcd-crypto.c new file +6
-0+void ufshcd_crypto_setup_rq_keyslot_manager (struct ufs_hba *hba, +struct request_queue *q) +{ +if ((hba->caps &UFSHCD_CAP_CRYPTO )) +blk_ksm_register (&hba->ksm, q); +}
There's an extra pair of parentheses in the 'if'.
Quoted 11 lines
drivers/scsi/ufs/ufshcd-crypto.h new file +5
-0@@ -0,0 +1,44 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* Copyright 2019 Google LLC +*/ +
drivers/scsi/ufs/ufshcd-crypto.h line 15
Quoted 10 lines
drivers/scsi/ufs/ufshcd-crypto.h new file +10
-0+#ifndef _UFSHCD_CRYPTO_H +#define _UFSHCD_CRYPTO_H + +#ifdef CONFIG_SCSI_UFS_CRYPTO +#include "ufshcd.h" +#include "ufshci.h" + +bool ufshcd_crypto_enable (struct ufs_hba *hba); + +void ufshcd_crypto_disable (struct ufs_hba *hba);
ufshcd_crypto_disable() has been removed, so its declaration should be removed too.
- Eric
PATCH v9 7/11 scsi: ufs: Add inline encryption support to UFS
In reply to Satya TangiralaWire up ufshcd.c with the UFS Crypto API, the block layer inline encryption additions and the keyslot manager.
--- drivers/scsi/ufs/ufshcd-crypto.h | 18 +++++++++++++ drivers/scsi/ufs/ufshcd.c | 44 ++++++++++++++++++++++++++++---- drivers/scsi/ufs/ufshcd.h | 6 +++++ 3 files changed, 63 insertions(+), 5 deletions(-)
drivers/scsi/ufs/ufshcd-crypto.h +18 -0
@@ -10,6 +10,20 @@#include "ufshcd.h" #include "ufshci.h" +static inline void ufshcd_prepare_lrbp_crypto (struct ufs_hba *hba, +struct scsi_cmnd *cmd, +struct ufshcd_lrb *lrbp) +{ +struct request *rq = cmd->request; + +if (rq->crypt_keyslot) { + lrbp->crypto_key_slot =blk_ksm_get_slot_idx (rq->crypt_keyslot); + lrbp->data_unit_num = rq->crypt_ctx->bc_dun[0 ]; + }else { + lrbp->crypto_key_slot =-1 ; + } +} +bool ufshcd_crypto_enable (struct ufs_hba *hba);void ufshcd_crypto_disable (struct ufs_hba *hba);
@@ -23,6 +37,10 @@ void ufshcd_crypto_destroy_keyslot_manager(struct ufs_hba *hba);#else /* CONFIG_SCSI_UFS_CRYPTO */ +static inline void ufshcd_prepare_lrbp_crypto (struct ufs_hba *hba, +struct scsi_cmnd *cmd, +struct ufshcd_lrb *lrbp) { } +static inline bool ufshcd_crypto_enable (struct ufs_hba *hba) {return false;
drivers/scsi/ufs/ufshcd.c +39 -5
111 lines not on this page · raw message
drivers/scsi/ufs/ufshcd.h +6 -0
@@ -168,6 +168,8 @@ struct ufs_pm_lvl_states {* @intr_cmd: Interrupt command (doesn't participate in interrupt aggregation) * @issue_time_stamp: time stamp for debug purposes * @compl_time_stamp: time stamp for statistics +* @crypto_key_slot: the key slot to use for inline crypto +* @data_unit_num: the data unit number for the first block for inline crypto * @req_abort_skip: skip request abort task flag */ struct ufshcd_lrb {
@@ -192,6 +194,10 @@ struct ufshcd_lrb {bool intr_cmd;ktime_t issue_time_stamp;ktime_t compl_time_stamp; +#if IS_ENABLED (CONFIG_SCSI_UFS_CRYPTO ) +int crypto_key_slot; +u64 data_unit_num; +#endif bool req_abort_skip; };
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerRe: [PATCH v9 07/11] scsi: ufs: Add inline encryption support to UFS
Quoted 4 lines · Satya Tangirala
Wire up
ufshcd.cwith the UFS Crypto API, the block layer inline encryption additions and the keyslot manager.Signed-off-by Satya Tangirala <[email protected]>
Thanks, like the previous patch this looks much better now!
A couple minor nits I noticed while reading this latest version:
drivers/scsi/ufs/ufshcd.h struct ufs_pm_lvl_states { · line 171
Quoted 9 lines
drivers/scsi/ufs/ufshcd.h +1
-0@@ -168,6 +168,8 @@ struct ufs_pm_lvl_states {* @intr_cmd: Interrupt command (doesn't participate in interrupt aggregation) * @issue_time_stamp: time stamp for debug purposes * @compl_time_stamp: time stamp for statistics +* @crypto_key_slot: the key slot to use for inline crypto
It would be helpful if the comment mentioned the -1 case:
* @crypto_key_slot: the key slot to use for inline crypto (-1 if none)
drivers/scsi/ufs/ufshcd.h struct ufshcd_lrb { · line 200
Quoted 12 lines
drivers/scsi/ufs/ufshcd.h +5
-0+* @data_unit_num: the data unit number for the first block for inline crypto * @req_abort_skip: skip request abort task flag */ struct ufshcd_lrb {@@ -192,6 +194,10 @@ struct ufshcd_lrb {bool intr_cmd;ktime_t issue_time_stamp;ktime_t compl_time_stamp; +#if IS_ENABLED (CONFIG_SCSI_UFS_CRYPTO ) +int crypto_key_slot; +u64 data_unit_num; +#endif
Since CONFIG_SCSI_UFS_CRYPTO is a bool this should use #ifdef, not IS_ENABLED().
- Eric
PATCH v9 8/11 fs: introduce SB_INLINECRYPT
In reply to Satya TangiralaIntroduce SB_INLINECRYPT, which is set by filesystems that wish to use blk-crypto for file content en/decryption.
--- fs/proc_namespace.c | 1 + include/linux/fs.h | 1 + 2 files changed, 2 insertions(+)
fs/proc_namespace.c +1 -0
@@ -49,6 +49,7 @@ static int show_sb_opts(struct seq_file *m, struct super_block *sb) { SB_DIRSYNC, ",dirsync" }, { SB_MANDLOCK, ",mand" }, { SB_LAZYTIME, ",lazytime" }, + { SB_INLINECRYPT, ",inlinecrypt" }, { 0, NULL } };const struct proc_fs_info *fs_infop;
include/linux/fs.h +1 -0
@@ -1371,6 +1371,7 @@ extern int send_sigurg(struct fown_struct *fown);#define SB_NODIRATIME 2048/* Do not update directory access times */ #define SB_SILENT 32768#define SB_POSIXACL (1<<16)/* VFS does not apply the umask */ +#define SB_INLINECRYPT (1<<17)/* Use blk-crypto for encrypted files */ #define SB_KERNMOUNT (1<<22)/* this is a kern_mount call */ #define SB_I_VERSION (1<<23)/* Update inode I_version field */ #define SB_LAZYTIME (1<<25)/* Update the on-disk [acm]times lazily */
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerRe: [PATCH v9 08/11] fs: introduce SB_INLINECRYPT
Quoted 4 lines · Satya Tangirala
Introduce
SB_INLINECRYPT, which is set by filesystems that wish to use blk-crypto for file content en/decryption.Signed-off-by Satya Tangirala <[email protected]>
This commit message could use a better explanation. E.g. this flag maps to the '-o inlinecrypt' mount option which multiple filesystems will implement, and code in fs/crypto/ needs to be able to check for this mount option in a filesystem-independent way.
- Eric
PATCH v9 9/11 fscrypt: add inline encryption support
In reply to Satya TangiralaAdd support for inline encryption to fs/crypto/. With "inline encryption", the block layer handles the decryption/encryption as part of the bio, instead of the filesystem doing the crypto itself via Linux's crypto API. This model is needed in order to take advantage of the inline encryption hardware present on most modern mobile SoCs.
To use inline encryption, the filesystem needs to be mounted with '-o inlinecrypt'. The contents of any encrypted files will then be encrypted using blk-crypto, instead of using the traditional filesystem-layer crypto. Fscrypt still provides the key and IV to use, and the actual ciphertext on-disk is still the same; therefore it's testable using the existing fscrypt ciphertext verification tests.
Note that since blk-crypto has a fallack to Linux's crypto API, and also supports all the encryption modes currently supported by fscrypt, this feature is usable and testable even without actual inline encryption hardware.
Per-filesystem changes will be needed to set encryption contexts when submitting bios and to implement the 'inlinecrypt' mount option. This patch just adds the common code.
--- fs/crypto/Kconfig | 6 + fs/crypto/Makefile | 1 + fs/crypto/bio.c | 51 ++++++ fs/crypto/crypto.c | 2 +- fs/crypto/fname.c | 4 +- fs/crypto/fscrypt_private.h | 120 +++++++++++-- fs/crypto/inline_crypt.c | 328 ++++++++++++++++++++++++++++++++++++ fs/crypto/keyring.c | 4 +- fs/crypto/keysetup.c | 92 ++++++---- fs/crypto/keysetup_v1.c | 16 +- include/linux/fscrypt.h | 57 +++++++ 11 files changed, 624 insertions(+), 57 deletions(-) create mode 100644 fs/crypto/inline_crypt.c
fs/crypto/Kconfig +6 -0
@@ -24,3 +24,9 @@ config FS_ENCRYPTION_ALGS select CRYPTO_SHA256 select CRYPTO_SHA512 select CRYPTO_XTS + +config FS_ENCRYPTION_INLINE_CRYPT + bool "Enable fscrypt to use inline crypto" + depends on FS_ENCRYPTION && BLK_INLINE_ENCRYPTION + help + Enable fscrypt to use inline encryption hardware if available.
fs/crypto/Makefile +1 -0
@@ -11,3 +11,4 @@ fscrypto-y := crypto.o \ policy.o fscrypto-$(CONFIG_BLOCK) += bio.o +fscrypto-$(CONFIG_FS_ENCRYPTION_INLINE_CRYPT) += inline_crypt.o
fs/crypto/bio.c +51 -0
69 lines not on this page · raw message
fs/crypto/crypto.c +1 -1
@@ -95,7 +95,7 @@ int fscrypt_crypt_block(const struct inode *inode, fscrypt_direction_t rw,DECLARE_CRYPTO_WAIT (wait);struct scatterlist dst, src;struct fscrypt_info *ci = inode->i_crypt_info; -struct crypto_skcipher *tfm = ci->ci_ctfm; +struct crypto_skcipher *tfm = ci->ci_key.tfm;int res =0 ;if (WARN_ON_ONCE (len <=0 ))
fs/crypto/fname.c +2 -2
@@ -117,7 +117,7 @@ int fscrypt_fname_encrypt(const struct inode *inode, const struct qstr *iname,struct skcipher_request *req =NULL ;DECLARE_CRYPTO_WAIT (wait);const struct fscrypt_info *ci = inode->i_crypt_info; -struct crypto_skcipher *tfm = ci->ci_ctfm; +struct crypto_skcipher *tfm = ci->ci_key.tfm;union fscrypt_iv iv;struct scatterlist sg;int res;
@@ -170,7 +170,7 @@ static int fname_decrypt(const struct inode *inode,DECLARE_CRYPTO_WAIT (wait);struct scatterlist src_sg, dst_sg;const struct fscrypt_info *ci = inode->i_crypt_info; -struct crypto_skcipher *tfm = ci->ci_ctfm; +struct crypto_skcipher *tfm = ci->ci_key.tfm;union fscrypt_iv iv;int res;
fs/crypto/fscrypt_private.h +107 -13
177 lines not on this page · raw message
fs/crypto/inline_crypt.c new file +328 -0
328 lines not on this page · raw message
fs/crypto/keyring.c +2 -2
@@ -44,8 +44,8 @@ static void free_master_key(struct fscrypt_master_key *mk)wipe_master_key_secret (&mk->mk_secret);for (i =0 ; i <= __FSCRYPT_MODE_MAX; i++) { -crypto_free_skcipher (mk->mk_direct_tfms[i]); -crypto_free_skcipher (mk->mk_iv_ino_lblk_64_tfms[i]); +fscrypt_destroy_prepared_key (&mk->mk_direct_keys[i]); +fscrypt_destroy_prepared_key (&mk->mk_iv_ino_lblk_64_keys[i]); }key_put (mk->mk_users);
fs/crypto/keysetup.c +62 -30
177 lines not on this page · raw message
fs/crypto/keysetup_v1.c +7 -9
@@ -146,7 +146,7 @@ struct fscrypt_direct_key {struct hlist_node dk_node;refcount_t dk_refcount;const struct fscrypt_mode *dk_mode; -struct crypto_skcipher *dk_ctfm; +struct fscrypt_prepared_key dk_key;u8 dk_descriptor[FSCRYPT_KEY_DESCRIPTOR_SIZE ];u8 dk_raw[FSCRYPT_MAX_KEY_SIZE ]; };
@@ -154,7 +154,7 @@ struct fscrypt_direct_key {static void free_direct_key (struct fscrypt_direct_key *dk) {if (dk) { -crypto_free_skcipher (dk->dk_ctfm); +fscrypt_destroy_prepared_key (&dk->dk_key);kzfree (dk); } }
@@ -199,6 +199,8 @@ find_or_insert_direct_key(struct fscrypt_direct_key *to_insert,continue ;if (ci->ci_mode != dk->dk_mode)continue ; +if (!fscrypt_is_key_prepared (&dk->dk_key, ci)) +continue ;if (crypto_memneq (raw_key, dk->dk_raw, ci->ci_mode->keysize))continue ;/* using existing tfm with same (descriptor, mode, raw_key) */
@@ -231,13 +233,9 @@ fscrypt_get_direct_key(const struct fscrypt_info *ci, const u8 *raw_key)return ERR_PTR (-ENOMEM );refcount_set (&dk->dk_refcount,1 ); dk->dk_mode = ci->ci_mode; - dk->dk_ctfm =fscrypt_allocate_skcipher (ci->ci_mode, raw_key, - ci->ci_inode); -if (IS_ERR (dk->dk_ctfm)) { - err =PTR_ERR (dk->dk_ctfm); - dk->dk_ctfm =NULL ; + err =fscrypt_prepare_key (&dk->dk_key, raw_key, ci); +if (err) goto err_free_dk; - }memcpy (dk->dk_descriptor, ci->ci_policy.v1.master_key_descriptor,FSCRYPT_KEY_DESCRIPTOR_SIZE );memcpy (dk->dk_raw, raw_key, ci->ci_mode->keysize);
@@ -259,7 +257,7 @@ static int setup_v1_file_key_direct(struct fscrypt_info *ci,if (IS_ERR (dk))return PTR_ERR (dk); ci->ci_direct_key = dk; - ci->ci_ctfm = dk->dk_ctfm; + ci->ci_key = dk->dk_key;return 0 ; }
include/linux/fscrypt.h +57 -0
69 lines not on this page · raw message
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerRe: [PATCH v9 09/11] fscrypt: add inline encryption support
Quoted 10 lines · Satya Tangirala
fs/crypto/inline_crypt.c new file +10
-0+/* Enable inline encryption for this file if supported. */ +void fscrypt_select_encryption_impl (struct fscrypt_info *ci) +{ +const struct inode *inode = ci->ci_inode; +struct super_block *sb = inode->i_sb; + +/* The file must need contents encryption, not filenames encryption */ +if (!fscrypt_needs_contents_encryption (inode)) +return ; +
fs/crypto/inline_crypt.c line 47
Quoted 10 lines
fs/crypto/inline_crypt.c new file +10
-0+/* blk-crypto must implement the needed encryption algorithm */ +if (ci->ci_mode->blk_crypto_mode ==BLK_ENCRYPTION_MODE_INVALID ) +return ; + +/* The filesystem must be mounted with -o inlinecrypt */ +if (!(sb->s_flags &SB_INLINECRYPT )) +return ; + + ci->ci_inlinecrypt = true; +}
A bug I came across last week when writing a new test is that '-o inlinecrypt' can break some fscrypt settings because it enables blk-crypto even when CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK is unset and the hardware doesn't support the algorithm. For example, adding '-o inlinecrypt' can make Adiantum-encrypted files stop working, due to the hardware only supporting AES-XTS.
That's undesirable. Adding '-o inlinecrypt' should just make inline encryption be used where it can, and not break anything.
To fix this, we should make fscrypt_select_encryption_impl() only set ->ci_inlinecrypt if either blk-crypto-fallback is enabled or if all the filesystem's devices support the algorithm.
In v7+ of this patchset, this is a bit tricky because now blk_ksm_crypto_key_supported() takes in a 'struct blk_crypto_key', which fscrypt_select_encryption_impl() doesn't have available yet. Perhaps make blk_ksm_crypto_key_supported() a wrapper around a function like blk_ksm_crypto_setting_supported() that takes a new struct:
struct blk_crypto_setting {
enum blk_crypto_mode_num crypto_mode;
unsigned int data_unit_size;
unsigned int dun_bytes;
};Then maybe add blk_crypto_setting_supported() which returns true if either blk_ksm_crypto_key_supported() *or* blk-crypto-fallback is enabled.
- Eric
PATCH v9 10/11 f2fs: add inline encryption support
In reply to Satya TangiralaWire up f2fs to support inline encryption via the helper functions which fs/crypto/ now provides. This includes:
- Adding a mount option 'inlinecrypt' which enables inline encryption on encrypted files where it can be used.
- Setting the bio_crypt_ctx on bios that will be submitted to an inline-encrypted file.
- Not adding logically discontiguous data to bios that will be submitted to an inline-encrypted file.
- Not doing filesystem-layer crypto on inline-encrypted files.
--- Documentation/filesystems/f2fs.txt | 6 +++ fs/f2fs/compress.c | 2 +- fs/f2fs/data.c | 68 +++++++++++++++++++++++++----- fs/f2fs/super.c | 32 ++++++++++++++ 4 files changed, 97 insertions(+), 11 deletions(-)
Documentation/filesystems/f2fs.txt +6 -0
@@ -246,6 +246,12 @@ compress_extension=%s Support adding specified extension, so that f2fs can enab on compression extension list and enable compression on these file by default rather than to enable it via ioctl. For other files, we can still enable compression via ioctl. +inlinecrypt + Encrypt/decrypt the contents of encrypted files using the + blk-crypto framework rather than filesystem-layer encryption. + This allows the use of inline encryption hardware. The on-disk + format is unaffected. For more details, see + Documentation/block/inline-encryption.rst. ================================================================================ DEBUGFS ENTRIES
fs/f2fs/compress.c +1 -1
@@ -775,7 +775,7 @@ static int f2fs_write_compressed_pages(struct compress_ctx *cc, .need_lock = LOCK_RETRY, .io_type = io_type, .io_wbc = wbc, - .encrypted = f2fs_encrypted_file(cc->inode), + .encrypted = fscrypt_inode_uses_fs_layer_crypto(cc->inode), };struct dnode_of_data dn;struct node_info ni;
fs/f2fs/data.c +58 -10
142 lines not on this page · raw message
fs/f2fs/super.c +32 -0
@@ -137,6 +137,7 @@ enum { Opt_alloc, Opt_fsync, Opt_test_dummy_encryption, + Opt_inlinecrypt, Opt_checkpoint_disable, Opt_checkpoint_disable_cap, Opt_checkpoint_disable_cap_perc,
@@ -202,6 +203,7 @@ static match_table_t f2fs_tokens = { {Opt_alloc, "alloc_mode=%s"}, {Opt_fsync, "fsync_mode=%s"}, {Opt_test_dummy_encryption, "test_dummy_encryption"}, + {Opt_inlinecrypt, "inlinecrypt"}, {Opt_checkpoint_disable, "checkpoint=disable"}, {Opt_checkpoint_disable_cap, "checkpoint=disable:%u"}, {Opt_checkpoint_disable_cap_perc, "checkpoint=disable:%u%%"},
@@ -790,6 +792,13 @@ static int parse_options(struct super_block *sb, char *options)f2fs_info (sbi,"Test dummy encryption mode enabled" );#else f2fs_info (sbi,"Test dummy encryption mount option ignored" ); +#endif +break ; +case Opt_inlinecrypt: +#ifdef CONFIG_FS_ENCRYPTION_INLINE_CRYPT + sb->s_flags |=SB_INLINECRYPT ; +#else +f2fs_info (sbi,"inline encryption not supported" );#endif break ;case Opt_checkpoint_disable_cap_perc:
@@ -1574,6 +1583,8 @@ static void default_options(struct f2fs_sb_info *sbi)F2FS_OPTION (sbi).compress_log_size =MIN_COMPRESS_LOG_SIZE ;F2FS_OPTION (sbi).compress_ext_cnt =0 ; + sbi->sb->s_flags &= ~SB_INLINECRYPT ; +set_opt (sbi,BG_GC );set_opt (sbi,INLINE_XATTR );set_opt (sbi,INLINE_DATA );
@@ -2415,6 +2426,25 @@ static void f2fs_get_ino_and_lblk_bits(struct super_block *sb, *lblk_bits_ret =8 *sizeof (block_t); } +static int f2fs_get_num_devices (struct super_block *sb) +{ +struct f2fs_sb_info *sbi =F2FS_SB (sb); + +if (f2fs_is_multi_device (sbi)) +return sbi->s_ndevs; +return 1 ; +} + +static void f2fs_get_devices (struct super_block *sb, +struct request_queue **devs) +{ +struct f2fs_sb_info *sbi =F2FS_SB (sb); +int i; + +for (i =0 ; i < sbi->s_ndevs; i++) + devs[i] =bdev_get_queue (FDEV (i).bdev); +} +static const struct fscrypt_operations f2fs_cryptops = { .key_prefix ="f2fs:" , .get_context = f2fs_get_context,
@@ -2424,6 +2454,8 @@ static const struct fscrypt_operations f2fs_cryptops = { .max_namelen = F2FS_NAME_LEN, .has_stable_inodes = f2fs_has_stable_inodes, .get_ino_and_lblk_bits = f2fs_get_ino_and_lblk_bits, + .get_num_devices = f2fs_get_num_devices, + .get_devices = f2fs_get_devices, };#endif
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
PATCH v9 11/11 ext4: add inline encryption support
In reply to Satya TangiralaFrom: Eric Biggers <[email protected]>
Wire up ext4 to support inline encryption via the helper functions which fs/crypto/ now provides. This includes:
- Adding a mount option 'inlinecrypt' which enables inline encryption on encrypted files where it can be used.
- Setting the bio_crypt_ctx on bios that will be submitted to an inline-encrypted file.
Note: submit_bh_wbc() in fs/buffer.c also needed to be patched for this part, since ext4 sometimes uses ll_rw_block() on file data.
- Not adding logically discontiguous data to bios that will be submitted to an inline-encrypted file.
- Not doing filesystem-layer crypto on inline-encrypted files.
--- Documentation/admin-guide/ext4.rst | 6 ++++++ fs/buffer.c | 7 ++++--- fs/ext4/inode.c | 4 ++-- fs/ext4/page-io.c | 6 ++++-- fs/ext4/readpage.c | 11 ++++++++--- fs/ext4/super.c | 9 +++++++++ 6 files changed, 33 insertions(+), 10 deletions(-)
Documentation/admin-guide/ext4.rst +6 -0
@@ -395,6 +395,12 @@ When mounting an ext4 filesystem, the following option are accepted: Documentation/filesystems/dax.txt. Note that this option is incompatible with data=journal. + inlinecrypt + Encrypt/decrypt the contents of encrypted files using the blk-crypto + framework rather than filesystem-layer encryption. This allows the use + of inline encryption hardware. The on-disk format is unaffected. For + more details, see Documentation/block/inline-encryption.rst. + Data Mode ========= There are 3 different data modes:
fs/buffer.c +4 -3
@@ -331,9 +331,8 @@ static void decrypt_bh(struct work_struct *work)static void end_buffer_async_read_io (struct buffer_head *bh,int uptodate) {/* Decrypt if needed */ -if (uptodate &&IS_ENABLED (CONFIG_FS_ENCRYPTION ) && -IS_ENCRYPTED (bh->b_page->mapping->host) && -S_ISREG (bh->b_page->mapping->host->i_mode)) { +if (uptodate && +fscrypt_inode_uses_fs_layer_crypto (bh->b_page->mapping->host)) {struct decrypt_bh_ctx *ctx =kmalloc (sizeof (*ctx),GFP_ATOMIC );if (ctx) {
@@ -3085,6 +3084,8 @@ static int submit_bh_wbc(int op, int op_flags, struct buffer_head *bh,*/ bio =bio_alloc (GFP_NOIO ,1 ); +fscrypt_set_bio_crypt_ctx_bh (bio, bh,GFP_NOIO ); + bio->bi_iter.bi_sector = bh->b_blocknr * (bh->b_size >>9 );bio_set_dev (bio, bh->b_bdev); bio->bi_write_hint = write_hint;
fs/ext4/inode.c +2 -2
@@ -1089,7 +1089,7 @@ static int ext4_block_write_begin(struct page *page, loff_t pos, unsigned len, }if (unlikely (err)) {page_zero_new_buffers (page, from, to); - }else if (IS_ENCRYPTED (inode) &&S_ISREG (inode->i_mode)) { + }else if (fscrypt_inode_uses_fs_layer_crypto (inode)) {for (i =0 ; i < nr_wait; i++) {int err2;
@@ -3720,7 +3720,7 @@ static int __ext4_block_zero_page_range(handle_t *handle,/* Uhhuh. Read error. Complain and punt. */ if (!buffer_uptodate (bh)) goto unlock; -if (S_ISREG (inode->i_mode) &&IS_ENCRYPTED (inode)) { +if (fscrypt_inode_uses_fs_layer_crypto (inode)) {/* We expect the key to be set. */ BUG_ON (!fscrypt_has_encryption_key (inode)); err = fscrypt_decrypt_pagecache_blocks(page, blocksize,
fs/ext4/page-io.c +4 -2
@@ -404,6 +404,7 @@ static void io_submit_init_bio(struct ext4_io_submit *io,* __GFP_DIRECT_RECLAIM is set, see comments for bio_alloc_bioset(). */ bio =bio_alloc (GFP_NOIO ,BIO_MAX_PAGES ); +fscrypt_set_bio_crypt_ctx_bh (bio, bh,GFP_NOIO ); bio->bi_iter.bi_sector = bh->b_blocknr * (bh->b_size >>9 );bio_set_dev (bio, bh->b_bdev); bio->bi_end_io = ext4_end_bio;
@@ -420,7 +421,8 @@ static void io_submit_add_bh(struct ext4_io_submit *io, {int ret; -if (io->io_bio && bh->b_blocknr != io->io_next_block) { +if (io->io_bio && (bh->b_blocknr != io->io_next_block || + !fscrypt_mergeable_bio_bh (io->io_bio, bh))) { submit_and_retry:ext4_io_submit (io); }
@@ -508,7 +510,7 @@ int ext4_bio_write_page(struct ext4_io_submit *io,* (e.g. holes) to be unnecessarily encrypted, but this is rare and * can't happen in the common case of blocksize == PAGE_SIZE. */ -if (IS_ENCRYPTED (inode) &&S_ISREG (inode->i_mode) && nr_to_submit) { +if (fscrypt_inode_uses_fs_layer_crypto (inode) && nr_to_submit) {gfp_t gfp_flags =GFP_NOFS ;unsigned int enc_bytes =round_up (len,i_blocksize (inode));
fs/ext4/readpage.c +8 -3
@@ -195,7 +195,7 @@ static void ext4_set_bio_post_read_ctx(struct bio *bio, {unsigned int post_read_steps =0 ; -if (IS_ENCRYPTED (inode) &&S_ISREG (inode->i_mode)) +if (fscrypt_inode_uses_fs_layer_crypto (inode)) post_read_steps |=1 <<STEP_DECRYPT ;if (ext4_need_verity (inode, first_idx))
@@ -232,6 +232,7 @@ int ext4_mpage_readpages(struct address_space *mapping,const unsigned blkbits = inode->i_blkbits;const unsigned blocks_per_page =PAGE_SIZE >> blkbits;const unsigned blocksize =1 << blkbits; +sector_t next_block;sector_t block_in_file;sector_t last_block;sector_t last_block_in_file;
@@ -264,7 +265,8 @@ int ext4_mpage_readpages(struct address_space *mapping,if (page_has_buffers (page)) goto confused; - block_in_file = (sector_t )page->index << (PAGE_SHIFT - blkbits); + block_in_file = next_block = + (sector_t )page->index << (PAGE_SHIFT - blkbits); last_block = block_in_file + nr_pages * blocks_per_page; last_block_in_file = (ext4_readpage_limit (inode) + blocksize -1 ) >> blkbits;
@@ -364,7 +366,8 @@ int ext4_mpage_readpages(struct address_space *mapping,* This page will go to BIO. Do we need to send this * BIO off first? */ -if (bio && (last_block_in_bio != blocks[0 ] -1 )) { +if (bio && (last_block_in_bio != blocks[0 ] -1 || + !fscrypt_mergeable_bio (bio, inode, next_block))) { submit_and_realloc:submit_bio (bio); bio =NULL ;
@@ -376,6 +379,8 @@ int ext4_mpage_readpages(struct address_space *mapping,*/ bio =bio_alloc (GFP_KERNEL ,min_t (int, nr_pages,BIO_MAX_PAGES )); +fscrypt_set_bio_crypt_ctx (bio, inode, next_block, +GFP_KERNEL );ext4_set_bio_post_read_ctx (bio, inode, page->index);bio_set_dev (bio, bdev); bio->bi_iter.bi_sector = blocks[0 ] << (blkbits -9 );
fs/ext4/super.c +9 -0
@@ -1514,6 +1514,7 @@ enum { Opt_journal_path, Opt_journal_checksum, Opt_journal_async_commit, Opt_abort, Opt_data_journal, Opt_data_ordered, Opt_data_writeback, Opt_data_err_abort, Opt_data_err_ignore, Opt_test_dummy_encryption, + Opt_inlinecrypt, Opt_usrjquota, Opt_grpjquota, Opt_offusrjquota, Opt_offgrpjquota, Opt_jqfmt_vfsold, Opt_jqfmt_vfsv0, Opt_jqfmt_vfsv1, Opt_quota, Opt_noquota, Opt_barrier, Opt_nobarrier, Opt_err,
@@ -1611,6 +1612,7 @@ static const match_table_t tokens = { {Opt_noinit_itable, "noinit_itable"}, {Opt_max_dir_size_kb, "max_dir_size_kb=%u"}, {Opt_test_dummy_encryption, "test_dummy_encryption"}, + {Opt_inlinecrypt, "inlinecrypt"}, {Opt_nombcache, "nombcache"}, {Opt_nombcache, "no_mbcache"}, /* for backward compatibility */ {Opt_removed, "check=none"}, /* mount option from ext2/3 */
@@ -1898,6 +1900,13 @@ static int handle_mount_opt(struct super_block *sb, char *opt, int token,case Opt_nolazytime: sb->s_flags &= ~SB_LAZYTIME ;return 1 ; +case Opt_inlinecrypt: +#ifdef CONFIG_FS_ENCRYPTION_INLINE_CRYPT + sb->s_flags |=SB_INLINECRYPT ; +#else +ext4_msg (sb,KERN_ERR ,"inline encryption not supported" ); +#endif +return 1 ; }for (m = ext4_mount_opts; m->token != Opt_err; m++)
Signature · 1 line
2.25.1.696.g5e7596f4ac-goog
Eric Biggers
maintainerQuoted 3 lines · Satya Tangirala
This patch series adds support for Inline Encryption to the block layer, UFS, fscrypt, f2fs and ext4.
This patch series can also be retrieved from
Repo: https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git
Tag: inline-encryption-v9
I based it on v5.6-rc2 (same base commit as v7 and v8) since it still applies cleanly to it. You can see what changed from v8 by:
git diff inline-encryption-v8..inline-encryption-v9
or from v7 by:
git diff inline-encryption-v7..inline-encryption-v9
- Eric