blk_crypto_...capabilities(9)

📦 version 7.3.1, in nixpkgs unstable

✨ blk_crypto_...capabilities(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 this one is literally a page about blk_crypto_intersect_capabilities and it's shorter than my attention span, so let's go 🌸

💅 NAME 💅

blk_crypto_intersect_capabilities — restrict supported crypto capabilities by child device 🎀

like, the parent device doesn't get to keep any fancy crypto tricks that the child device can't do. intersection, bestie. girl math but for capabilities ✨

🦋 SYNOPSIS 🦋

void blk_crypto_intersect_capabilities (struct blk_crypto_profile
*parent , const struct blk_crypto_profile *child );

no return value, no drama, it just returns void and vibes 💀

🎀 ARGUMENTS 🎀

  • parent — the crypto profile for the parent device 👑 this is the one that gets its capabilities trimmed.
  • child — the crypto profile for the child device, or NULL. yes, NULL is a valid mood here 🙈

🌈 DESCRIPTION 🌈

So here's the tea, bestie 🍓 this clears all crypto capabilities in parent that aren't set in child. literally anything the child doesn't support? gone. not invited to the group chat anymore 💅

And if child is NULL? then this clears ALL parent capabilities. every single one. not me wiping the whole slate 😭

⚠️ Only use this when setting up the crypto profile for a layered device, before it's been exposed yet. like, do NOT come in here trying this on a device that's already out there living its main character life — that's not the vibe and the page says so directly 🫶

⭐ SEE ALSO ⭐

Kernel file ./block/blk-crypto-profile.c (iykyk 🔥), plus these iconic siblings:

🧚 and that's the whole page, bestie! this masterpiece lives in ./block, dated October 2026, and it's part of the Kernel API Manual — go forth and intersect those capabilities 💜✨

📦 where this page comes from