BLK-CRYPTO PROFILES(9)

blk-crypto profiles 💖

okay so bestie, this is the blk-crypto profiles(9) page from the Kernel API Manual, and it’s literally about the state for a particular inline encryption device. ✨ A blk_crypto_profile serves as the way that drivers for inline encryption hardware expose their crypto capabilities and certain functions (e.g., functions to program and evict keys) to upper layers. Device drivers that want to support inline encryption construct a crypto profile, then associate it with the disk’s request_queue. 🫶

If the device has keyslots, then its blk_crypto_profile also handles managing these keyslots in a device-independent way, using the driver-provided functions to program and evict keys as needed. This includes keeping track of which key and how many I/O requests are using each keyslot, getting keyslots for I/O requests, and handling key eviction requests. 👑

For more information, see Documentation/block/inline-encryption.rst.

👀 SEE ALSO

• Kernel file ./block/blk-crypto-profile.c — the kernel file, iykyk.
• blk_crypto_profile_init(9)
• devm_blk_crypto_profile_init(9)
• blk_crypto_keyslot_index(9)
• blk_crypto_get_keyslot(9)
• blk_crypto_put_keyslot(9)
• blk_crypto_reprogram_all_keys(9)
• blk_crypto_derive_sw_secret(9)
• blk_crypto_intersect_capabilities(9)
• blk_crypto_has_capabilities(9)
• blk_crypto_update_capabilities(9)

mwah 💋 this page’s source/version is ./block and it’s dated October 2026 — slay and goodbye, bestie! 🌈