parse_tag_1_packet(9)
π parse_tag_1_packet(9) π
okay so bestie, welcome to the Kernel API Manual β¨ β yes the actual manual name, we're fancy here. today's main character is parse_tag_1_packet, and she is very specific about her arguments, so buckle up π«Ά
πΈ NAME πΈ
parse_tag_1_packet β
and honestly? the original page gives you literally NOTHING after that dash π like the description is just vibes and a hyphen. no cap. so we're gonna go straight to the synopsis, which is where the real tea is π
β SYNOPSIS β
int parse_tag_1_packet (struct ecryptfs_crypt_stat *crypt_stat ,
unsigned char *data , struct list_head *auth_tok_list , struct
ecryptfs_auth_tok **new_auth_tok , size_t *packet_size , size_t
max_packet_size );
six arguments, one int return, she's giving "i have a lot going on but i'm handling it" π₯
π¦ ARGUMENTS π¦
crypt_statβ the cryptographic context, and this function is gonna modify it based on whatever's inside the packet. so yeah, she's not just reading, she's editing. main character energy πdataβ the raw bytes of the packet. literally just the bytes, the whole bytes, nothing but the bytes πauth_tok_listβ so eCryptfs parses packets into authentication tokens, right? and for this packet, a new authentication token gets placed at the end of this list. end of list = where the new girl sits πnew_auth_tokβ pointer to a pointer to memory that this function allocates. it sets the memory address of the pointer toNULLon error (important!! π). this object gets added to theauth_tok_list.packet_sizeβ this function writes the size of the parsed packet into this memory location. zero on error. so if you see a0, something went sideways πmax_packet_sizeβ the maximum allowable packet size. the ceiling. the limit. respect it β¨
π DESCRIPTION π
Returns zero on success; non-zero on error.
that's it. that's the whole description. short and iconic, honestly π
lowkey the whole page is basically "here are my six arguments, here's my return value, bye" and i respect the minimalism fr fr π
πΈ SEE ALSO πΈ
- Kernel file
./fs/ecryptfs/keystore.c ecryptfs_parse_packet_length(9)ecryptfs_write_packet_length(9)ecryptfs_verify_version(9)ecryptfs_verify_auth_tok_from_key(9)ecryptfs_find_auth_tok_for_sig(9)ecryptfs_parse_tag_70_packet(9)decrypt_pki_encrypted_session_key(9)parse_tag_3_packet(9)parse_tag_11_packet(9)decrypt_passphrase_encrypted_session_key(9)ecryptfs_parse_packet_set(9)write_tag_1_packet(9)write_tag_11_packet(9)write_tag_3_packet(9)ecryptfs_generate_key_packet_set(9)
like a whole friend group of packet functions, and she's the tag-1 one π§ iykyk π¦
and that's the page!! it lives in ./fs/ecryptfs and it's dated October 2026 β so mark your calendar bestie, this one's from the future βπ bye bye π«Άπ
π¦ 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