fscrypt_free_inode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fscrypt_free_inode(9) β€” Kernel API Manual, but make it make sense

okay bestie, so this is a page from the Kernel API Manual and it's about one (1) little function that does one (1) little job. it's short, it's iconic, let's go 🫢


✨ NAME ✨

fscrypt_free_inode β€” literally just frees an inode's fscrypt data, and the kicker is that it requires an RCU delay. that's the whole personality. πŸŽ€


🌸 SYNOPSIS 🌸

void fscrypt_free_inode (struct inode *inode );

no return value, no drama, it just goes in there and does the thing. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • inode β€” an inode being freed. yes that's it. that's the argument. she's the main character and also the only character. πŸ‘‘

⭐ DESCRIPTION ⭐

so what does she actually do? she frees the inode's cached decrypted symlink target, if there even is one β€” and if there isn't, she's not bothered, she just moves on with her life. πŸ’–

here's the part you gotta remember though, no cap: filesystems must call this after an RCU grace period, and they gotta do it just before they free the inode. like, that's the vibe check on this whole function. don't come at her early, don't come at her late. timing is everything, iykyk. ⏰✨

fr fr, the ordering is not a suggestion β€” "must call this after an RCU grace period, just before they free the inode" is the assignment. πŸ“

πŸ”₯ SEE ALSO πŸ”₯

the whole fscrypt friend group honestly, go say hi to all of them πŸ’œ


aaaand that's the page!! πŸŽ€ she lives in ./fs/crypto, she's dated October 2026, and she answers to the name fscrypt_free_inode(9) β€” okay bye bestie, slay your inode cleanup πŸ§šβ€β™€οΈπŸŒΈπŸ’–

πŸ“¦ where this page comes from