STRUCT BLK_CRYPTO_PROFILE(9)

💖 struct blk_crypto_profile(9) 💖

okay so bestie, welcome to the kernel API manual, and today's main character is struct blk_crypto_profile — literally the inline encryption profile for a device. yes. we're doing cryptography. put your hair up, we're getting into it 🎀

---

✨ NAME ✨

struct blk_crypto_profile — inline encryption profile for a device 💅

---

🦋 SYNOPSIS 🦋

struct blk_crypto_profile {
    struct blk_crypto_ll_ops ll_ops;
    unsigned int max_dun_bytes_supported;
    unsigned int key_types_supported;
    unsigned int modes_supported[BLK_ENCRYPTION_MODE_MAX];
    struct device *dev;
 };

like, that's the whole vibe of it. five fields. she's compact. she's iconic. 👑

---

🌸 Members 🌸

• ll_ops — these are the driver-provided functions that control the inline encryption hardware — think programming keys and evicting keys. your driver brings the moves, this field holds them. 🫶
• max_dun_bytes_supported — the maximum number of bytes supported for specifying the data unit number (DUN). and specifically, the range of supported DUNs is 0 through (1 << (8 * max_dun_bytes_supported)) - 1. math is math, bestie, don't fight it. 🔥
• key_types_supported — a bitmask of the supported key types: BLK_CRYPTO_KEY_TYPE_RAW and/or BLK_CRYPTO_KEY_TYPE_HW_WRAPPED. bitmask girlies rise 🌈
• modes_supported — array of bitmasks that specifies whether each combination of crypto mode and data unit size is supported. specifically, the i'th bit of modes_supported[crypto_mode] is set if crypto_mode can be used with a data unit size of (1 << i). and note that only data unit sizes that are powers of 2 can be supported ✨ (so like, don't come at her with 3, she will not be entertaining it 💀)
• dev — an optional device for runtime power management. and if the driver provides this device, it will be runtime-resumed before any function in ll_ops is called, and will remain resumed during the call. she wakes up for the function call and stays up through the whole thing — main character energy fr fr 😭

---

💜 Description 💜

so what's actually in here? this struct contains three-ish things, and they're all doing their own little job:

• a storage device's inline encryption capabilities (e.g. the supported crypto algorithms)
• driver-provided functions to control the inline encryption hardware (e.g. programming and evicting keys)
• optional device-independent keyslot management data

that's the whole package. capabilities, control functions, and the optional keyslot-management situation. slay 🧚

---

⭐ SEE ALSO ⭐

• Kernel file ./include/linux/blk-crypto-profile.h
• struct blk_crypto_ll_ops(9)

---

lowkey a reminder: keep the fields exactly as they are up there in the synopsis, BLK_ENCRYPTION_MODE_MAX included, because that array size is not vibes-based, it's real 💀

---

aaaand that's the page!! this whole thing lives in ./include/linux, from the October 2026 Kernel API Manual, and it's all about struct blk_crypto_profile(9). go forth and encrypt inline, bestie 💖🎀🦋