ecryptfs_par...ag_70_packet(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ecryptfs_parse_tag_70_packet(9) πŸ’…

okay bestie, buckle up β€” we're in the Kernel API Manual today and this one's a whole function. no cap, it's giving "cryptographic packet parser that knows exactly what it's doing" and honestly? we're obsessed πŸŽ€


✨ NAME ✨

ecryptfs_parse_tag_70_packet β€” literally just parses and processes an FNEK-encrypted passphrase packet. that's the whole vibe. πŸ’–


🌸 SYNOPSIS 🌸

int ecryptfs_parse_tag_70_packet (char **filename , size_t
*filename_size , size_t *packet_size , struct ecryptfs_mount_crypt_stat
*mount_crypt_stat , char *data , size_t max_packet_size );

she takes six args and returns an int, periodt. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • filename β€” bestie, this function kmalloc's the memory for the filename. it's literally allocating it for you, so you don't have to 🫢
  • filename_size β€” this one gets set to the amount of memory that got kmalloc'd for the filename. so this pointer comes back knowing the size, iykyk.
  • packet_size β€” set to the number of octets in the packet that got parsed. octets!! not bytes, octets. respectful. ✨
  • mount_crypt_stat β€” the mount-wide cryptographic context. like the big-picture crypto mood board for the whole mount πŸ’œ
  • data β€” the memory location holding the start of the tag 70 packet. this is where the actual packet lives πŸŽ€
  • max_packet_size β€” the maximum legal size of the packet to be parsed from data. key word legal, so don't be out here passing shady sizes πŸ™ˆ

πŸ”₯ DESCRIPTION πŸ”₯

Returns zero on success; non-zero otherwise.

that's it. that's the description. iconic honestly β€” she said "my return value speaks for itself" and moved on πŸ’€

lowkey the most important line on this whole page though, so don't skip the vibe check on that return value 🧚

⭐ SEE ALSO ⭐

Kernel file ./fs/ecryptfs/keystore.c, plus the whole extended friend group:

not me listing fifteen cross-references like it's a group chat roll call 😭 but every single one of them ate, fr fr πŸ”₯


and that's the whole page, babe 🌈 brought to you by the fine folks over in ./fs/ecryptfs, dated October 2026 β€” so go forth, parse that tag 70 packet, and slay πŸ‘‘πŸ’–

πŸ“¦ where this page comes from