Lines Matching refs:t

32 drives don't provide fine-grained control of encryption and provide no way to
63   slow and there may not be very many keyslots, we shouldn't just program the
73   encryption support of their underlying devices.  However, it doesn't make
90 layer and device drivers.  Note that the encryption context doesn't explicitly
104 specify encryption contexts and don't need to know about keyslots at all, nor do
112 keyslot (a keyslot that isn't in-use by any I/O), then programs the key into the
145 block_device that doesn't support that encryption context, the block layer will
170 encryption hardware, the crypto API doesn't accept keys directly in requests but
172 expensive; moreover, allocating a crypto_skcipher can't happen on the I/O path
206 for en/decryption.  Users don't need to worry about freeing the bio_crypt_ctx
248 the blk_crypto_profile, so drivers don't need to worry about handling
253 If the driver implements runtime suspend and its blk_crypto_ll_ops don't work
296 Because there isn't any real hardware yet, it seems prudent to assume that