crypt_scatterlist(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« NAME πŸ’«

ok so bestie, this is crypt_scatterlist β€” and like, the original page literally leaves the description blank after the dash? iconic honestly. no description, no notes, just vibes. it's a kernel API manual entry for crypt_scatterlist, and yes that's all the NAME section gives us, we respect the mystery 🫢


✨ SYNOPSIS ✨

int crypt_scatterlist (struct ecryptfs_crypt_stat *crypt_stat , struct
scatterlist *dst_sg , struct scatterlist *src_sg , int size , unsigned
char *iv , int op );

πŸŽ€ ARGUMENTS πŸŽ€

okay bestie here's the cast of characters, main character energy only:

  • crypt_stat β€” pointer to the crypt_stat struct you're gonna initialize. it's giving setup era πŸ’…
  • dst_sg β€” the destination of the data after the crypto operation goes down. where the glow-up lands ✨
  • src_sg β€” the data that's about to get encrypted or decrypted. the before picture πŸ“Έ
  • size β€” length of data. how much we're working with, no cap.
  • iv β€” the IV to use. yes, that IV. the initialization vector. keep up πŸ’œ
  • op β€” ENCRYPT or DECRYPT, to indicate the desired operation. you literally just tell it which one, pick your fighter πŸ”₯

🌸 DESCRIPTION 🌸

so what does it actually do?? it returns the number of bytes encrypted or decrypted β€” that's the number you want, that's the slay ✨

⚠️ heads up: a negative value on error. so if the number comes back negative, that's not a cute number, that's an error, and you should be like "😭 okay something's wrong."

πŸ¦‹ SEE ALSO πŸ¦‹

kernel file ./fs/ecryptfs/crypto.c β€” go read it, it's right there:

like, that's the whole friend group right there πŸ’–


and that's the page!! 🧚

this lil masterpiece lives in <pink>./fs/ecryptfs</pink> and it's dated October 2026 β€” source/version and date, both accounted for, we did not forget a single crumb πŸ“

crypt_scatterlist(9) β€” periodt. πŸ’…πŸ‘‘

πŸ“¦ where this page comes from