fscrypt_fname_free_buffer(9)

✨ fscrypt_fname_free_buffer ✨

okay so bestie, we're in the kernel API manual today — the fscrypt_fname_free_buffer(9) page specifically 💅 this is the little cleanup era of the fscrypt filename saga, and honestly it's giving responsible adult energy.

---

🌸 NAME 🌸

fscrypt_fname_free_buffer — free a buffer for presented filenames 🎀

---

🦋 SYNOPSIS 🦋

void fscrypt_fname_free_buffer (struct fscrypt_str *crypto_str );

no cap, that's the whole signature. void return, so like… she doesn't report back. she just does her job and leaves. main character behavior honestly 👑

---

🍓 ARGUMENTS 🍓

• crypto_str — the buffer to free. that's it. that's the argument. she's the one getting released from her obligations 🫶

---

💜 DESCRIPTION 💜

Free a buffer that was allocated by fscrypt_fname_alloc_buffer.

literally that's the vibe 🧚 she's the counterpart, the cleanup crew, the "you brought a buffer into this world, now let her go" moment. if fscrypt_fname_alloc_buffer is the girl who showed up with the snacks, fscrypt_fname_free_buffer is the one who makes sure nothing gets left behind at the function's house 😭💀

just a lil note: this only makes sense for buffers that actually came from fscrypt_fname_alloc_buffer. don't be out here freeing random stuff, bestie 🙈

---

🌈 SEE ALSO 🌈

Kernel file ./fs/crypto/fname.c — plus the whole friend group:

• fscrypt_fname_encrypt(9)
• fname_decrypt(9)
• fscrypt_fname_encrypted_size(9)
• fscrypt_fname_alloc_buffer(9)
• fscrypt_fname_disk_to_usr(9)
• fscrypt_setup_filename(9)
• fscrypt_match_name(9)
• fscrypt_fname_siphash(9)

it's giving squad goals, fr fr 🔥👑

---

and that's the page!! mwah 💖 this little icon lives under ./fs/crypto, dated October 2026, and yes the manual calls her fscrypt_fname_free_buffer(9) — remember her name, she's the one who cleans up after everybody else 🎀✨