ecryptfs_co..._inode_flags(9)
πΈ ecryptfs_copy_mount_wide_flags_to_inode_flags(9) πΈ
okay so this is a page from the Kernel API Manual bestie, and the page name is honestly too long for the header so it gets squished down to ecryptfs_co..._inode_flags(9) β yes that's the real, official, truncated vibe. iykyk π
β¨ NAME β¨
ecryptfs_copy_mount_wide_flags_to_inode_flags β that's it, that's the name, no little dash description after it, the manpage just leaves us hanging π«Ά
π¦ SYNOPSIS π¦
void ecryptfs_copy_mount_wide_flags_to_inode_flags (struct
ecryptfs_crypt_stat *crypt_stat , struct ecryptfs_mount_crypt_stat
*mount_crypt_stat );
it returns void, so likeβ¦ no return value, no exit status, nothing to check. it just does the thing and moves on. main character energy fr β¨
π ARGUMENTS π
crypt_statβ the inode's cryptographic context π this is the one getting stuff copied into.mount_crypt_statβ the mount point's cryptographic context πΈ this is the one the flags come from.
π DESCRIPTION π
so what does it actually do? literally what it says on the tin: this function propagates the mount-wide flags to individual inode flags. mount-wide β‘οΈ inode-level. the flags travel. slay π«
no extra options, no hidden defaults, no environment variables, nothing sneaky β just a straight-up copy of flags from the mount's crypt stat into the inode's crypt stat. clean, simple, iconic. periodt.
π SEE ALSO π
the Kernel file ./fs/ecryptfs/crypto.c β that's where the whole squad lives, and here's every single one of them, no cap, all of them, in order π
ecryptfs_from_hex(9)ecryptfs_derive_iv(9)ecryptfs_init_crypt_stat(9)ecryptfs_destroy_crypt_stat(9)virt_to_scatterlist(9)crypt_scatterlist(9)crypt_extent(9)ecryptfs_encrypt_page(9)ecryptfs_decrypt_page(9)ecryptfs_init_crypt_ctx(9)ecryptfs_set_default_crypt_stat_vals(9)ecryptfs_new_file_context(9)ecryptfs_validate_marker(9)ecryptfs_process_flags(9)write_ecryptfs_marker(9)ecryptfs_code_for_cipher_string(9)ecryptfs_cipher_code_to_string(9)ecryptfs_write_headers_virt(9)ecryptfs_write_metadata(9)set_default_header_data(9)ecryptfs_read_headers_virt(9)ecryptfs_read_xattr_region(9)ecryptfs_process_key_cipher(9)ecryptfs_destroy_crypto(9)ecryptfs_tfm_exists(9)ecryptfs_get_tfm_and_mutex_for_cipher_name(9)ecryptfs_encode_for_filename(9)ecryptfs_decode_from_filename(9)ecryptfs_encrypt_and_encode_filename(9)ecryptfs_decode_and_decrypt_filename(9)
go read them all bestie, they're all in ./fs/ecryptfs and they all ate π₯
no warnings, no bugs, no deprecation drama on this one β it's just a flag-copying cutie π§
that's the whole page!! mwah π this one's from the ./fs/ecryptfs source tree, October 2026 era, and yes the footer still calls it ecryptfs_co..._inode_flags(9) because some names are just too iconic to fit. bye bestie, go copy some flags ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms