blk_crypto_...ecrypt_endio(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… blk_crypto_...ecrypt_endio(9) β€” Kernel API Manual πŸŽ€

okay so bestie, we're in the Kernel API Manual today and this page is literally about one tiny function that does a very specific little job. no cap, it's short, but it's important, so let's get into it πŸ’–


✨ NAME ✨

blk_crypto_fallback_decrypt_endio β€” the one that queues a bio for fallback decryption πŸ¦‹


🌸 SYNOPSIS 🌸

void blk_crypto_fallback_decrypt_endio (struct bio *bio );

that's it. that's the whole signature. she's lowkey minimal and we respect it πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • bio β€” the bio we're queueing. that's the whole vibe. she's the main character here πŸ’…

πŸ’œ DESCRIPTION πŸ’œ

okay so picture this: we gotta restore bi_private and bi_end_io, and then queue the bio for decryption into a workqueue.

and why are we doing the queue thing instead of just, like, doing it right there? because β€” and this is the important part, don't skip it β€” this function will be called from an atomic context 😭 so you literally cannot just go off and do the decryption inline. that's not the move. into the workqueue it goes, periodt ✨

fr fr, the atomic-context thing is the whole reason this function exists. respect the constraint or the kernel will simply not have a good time πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./block/blk-crypto-fallback.c β€” the whole source, go read her 🌈
  • blk_crypto_fallback_bio_prep(9) β€” the sibling function, iykyk 🫢

and that's the page bestie!! 🧚 from ./block (that's the source, mwah) and dated October 2026 β€” stay caffeinated, stay cryptographically safe, and remember: atomic context means no blocking, no exceptions πŸ’–πŸ’…β­πŸ“

πŸ“¦ where this page comes from