Lines Matching refs:keyslot

21 algorithm, and data unit size first be programmed into a keyslot.  Each
22 low-level I/O request then just contains a keyslot index and data unit number.
65   keyslots and reuse an already-programmed keyslot when possible.
105 device drivers need to care about most details of keyslot management.
107 Specifically, for each keyslot, the block layer (via the blk_crypto_profile)
108 keeps track of which blk_crypto_key that keyslot contains (if any), and how many
110 ``struct request`` for a bio that has an encryption context, it grabs a keyslot
112 keyslot (a keyslot that isn't in-use by any I/O), then programs the key into the
113 least-recently-used idle keyslot using the function the device driver provided.
114 In both cases, the resulting keyslot is stored in the ``crypt_keyslot`` field of
130 includes getting a keyslot from the clone's target device if needed.
137 likewise for the block layer's keyslot management logic.  It is also desirable
168 for this is twofold.  First, it allows the keyslot management logic to be tested
251 also have a keyslot which was already programmed with the appropriate key.