ecryptfs_get..._cipher_name(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

omg hi bestie πŸ’– welcome to ecryptfs_get..._cipher_name(9) from the Kernel API Manualβ€”yes, that's the whole manual name, and no we are not abbreviating her, she's iconic like that. This is the kernel crypto matchmaker page, and we're keeping every pointer, return value, and reference intact. No cap. 🫢

✨ NAME ✨

  • ecryptfs_get_tfm_and_mutex_for_cipher_name -

that's it, that's the name listing; the original line ends with a dash and leaves the summary slot mysteriously empty, and honestly? mysterious main character energy. πŸ’…

🌸 SYNOPSIS 🌸

here's the function signature, copied exactly because we do not play with code around here:

       int ecryptfs_get_tfm_and_mutex_for_cipher_name (struct crypto_skcipher
       **tfm , struct mutex **tfm_mutex , char *cipher_name );

πŸŽ€ ARGUMENTS πŸŽ€

okay so the function takes three pointers and they all matter:

  • tfm β€” gets set to the cached tfm that was found, or to the new tfm that got created. like a little pointer handoff, slay ✨
  • tfm_mutex β€” gets set to the mutex for the cached tfm that was found, or for the new tfm that got created. lock vibe check complete πŸ”’
  • cipher_name β€” the name of the cipher to search for and/or add. yes, search and/or add, she contains multitudes πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does ecryptfs_get_tfm_and_mutex_for_cipher_name actually do? it sets pointers to tfm & tfm_mutex matching cipher_name. first it searches for a cached item, and if it doesn't find one, it creates a new one. very "if you can't find your fave in the group chat, make a new group chat" energy.

return value tea β˜•: 0 on success, and non-zero if adding the new cipher failed. that's the whole vibe check, fr fr.

🌈 SEE ALSO 🌈

Kernel file ./fs/ecryptfs/crypto.c and the whole iconic friend group:

okay that's the page bestie πŸ’– this little icon lives in the source tree as ./fs/ecryptfs, it's dated October 2026, and the manual entry is ecryptfs_get..._cipher_name(9). mwah, go call your nearest kernel crypto function responsibly βœ¨πŸ‘‘

πŸ“¦ where this page comes from