blk_crypto_get_keyslot(9)

📦 version 7.3.1, in nixpkgs unstable

💅 blk_crypto_get_keyslot 💅

okay so this is a page from the Kernel API Manual (yes bestie, blk_crypto_get_keyslot(9), section 9, we're in kernel-doc territory now 🎀) and it's literally about grabbing a keyslot for a key if needed. that's it. that's the whole vibe. let's get into it ✨

✨ NAME ✨

blk_crypto_get_keyslot — get a keyslot for a key, if needed. no cap, that's the entire job 🫶

🌸 SYNOPSIS 🌸

blk_status_t blk_crypto_get_keyslot (struct blk_crypto_profile *profile
, const struct blk_crypto_key *key , struct blk_crypto_keyslot
**slot_ptr );

🦋 ARGUMENTS 🦋

  • profile — the crypto profile of the device the key is gonna be used on 💖
  • key — the key that will be used 🔑
  • slot_ptr — okay so if a keyslot gets allocated, an opaque pointer to the keyslot struct gets stored here. and heads up: you must call blk_crypto_put_keyslot later to release it, no skipping that step bestie 😭 otherwise, NULL gets stored here.

🧚 DESCRIPTION 🧚

so if the device has keyslots, this gets you a keyslot that's been programmed with the specified key. and if the key is already in a slot? it just reuses it, iconic, no wasted work 💅 otherwise it waits for a slot to become idle and programs the key into it. patient queen behavior honestly 👑

⭐ CONTEXT ⭐

Process context. it takes and releases profile->lock. 🔒

💜 RETURN 💜

BLK_STS_OK on success — which means either a keyslot was allocated or one wasn't even needed — or a blk_status_t error on failure. simple as that 🍓

🌈 SEE ALSO 🌈

seriously tho, go read blk_crypto_put_keyslot(9) if you took a slot. don't leave it hanging, that's so not main character energy 🙈

and that's the whole page!! 💖 this one lives in ./block, dated October 2026, and it's literally blk_crypto_get_keyslot(9) — go program some keys, bestie, you got this 🔥👑

📦 where this page comes from