Lines Matching full:fallback

27 To allow for testing, we also want a crypto API fallback when actual
84 blk-mq changes, other block layer changes and blk-crypto-fallback
93 We introduce ``block/blk-crypto-fallback.c``, which allows upper layers to remain
97 en/decrypt the bio with the blk-crypto-fallback.
102 concerned). ``blk-crypto-fallback`` sets the bounce bio's ``bi_end_io`` to an
106 is saved and overwritten by ``blk-crypto-fallback`` to
114 blk-crypto-fallback is used, the ciphertext written to disk (and hence the
120 ``blk-crypto-fallback``. We will eventually reach a point in blk-mq when a
154 blk-crypto-fallback, if hardware support isn't available for the desired
160 (either by real inline encryption hardware, or by the blk-crypto-fallback).
161 This is useful e.g. when blk-crypto-fallback is disabled, and the upper layer
164 and the upper layer can fallback to something else if appropriate.
169 hardware supports the key's crypto settings, or the crypto API fallback has
178 inline encryption hardware that the key might have been programmed into (or the blk-crypto-fallback…
252 encryption support is present or the kernel crypto API fallback is used (since
253 if the fallback is used, the device will receive the integrity info of the
261 to NULL). When the crypto API fallback is enabled, this means that all bios with
262 and encryption context will use the fallback, and IO will complete as usual.
263 When the fallback is disabled, a bio with an encryption context will be failed.