ceph_fscrypt...rypt_extents(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, this page is ceph_fscrypt_decrypt_extents from the Kernel API Manual β€” page ceph_fscrypt...rypt_extents(9) β€” and it's literally here to decrypt received extents in given buffer. that's the whole vibe. πŸ’…


🌸 SYNOPSIS 🌸

int ceph_fscrypt_decrypt_extents (struct inode *inode , struct page
       **page , u64 off , struct ceph_sparse_extent *map , u32 ext_cnt );

πŸŽ€ ARGUMENTS πŸŽ€

  • inode β€” the inode associated with pages being decrypted. it's the main-character inode, basically.
  • page β€” pointer to page array. yes, pages plural, she contains multitudes.
  • off β€” offset into the file that the data in page[0] starts. so you know exactly where the tea begins.
  • map β€” pointer to extent array. the map, the blueprint, the layout.
  • ext_cnt β€” length of extent array. gotta know how many extents we're working with, fr fr.

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: you give it an extent map and a page array, and it decrypts the received data in-place, skipping holes like they're irrelevant. no cap, holes do not get decrypted.

Returns the offset into buffer of end of last decrypted block. that's the return value, bestie β€” the end-of-last-decrypted-block offset. ✨

πŸ’– SEE ALSO πŸ’–


mwah πŸ’‹ shoutout to the source/version tag ./fs/ceph, the date October 2026, and the ceph_fscrypt...rypt_extents(9) manual β€” that's the sign-off, bestie. periodt. 🫢

πŸ“¦ where this page comes from