tomoyo_print_header(9)
π tomoyo_print_header β the Kernel API Manual, bestie edition π
okay so real talk, we're in the tomoyo_print_header(9) section of the Kernel API Manual and this little function is literally the intro queen of your audit log. She shows up first, she sets the vibe, everybody else follows. iykyk π
β¨ NAME β¨
tomoyo_print_header β get header line of audit log. that's it, that's the whole job, and she does it gorgeously π«Ά
β¨ SYNOPSIS β¨
char * tomoyo_print_header (struct tomoyo_request_info *r );
no cap, that's the exact signature, copy it character for character or the compiler will be sooo mad at you π
β¨ ARGUMENTS β¨
rβ pointer to"struct tomoyo_request_info". yes the quotes are part of the original, don't come for me, i'm just the messenger πΈ
β¨ DESCRIPTION β¨
returns string representation. that's the whole thing!! she hands you back a string and you go slay π
but bestie, listen, this is the important part: this function uses kmalloc, so the caller must kfree it β but only if this function didn't return NULL. literally do not free a NULL, that's not the move π
β οΈ memory check!!kmallocmeans somebody's gotta clean up and that somebody is you. if it returnedNULL, hands off. if it returned a real string,kfreethat thing or it's a leak and leaks are giving π©
β¨ SEE ALSO β¨
kernel file ./security/tomoyo/audit.c plus the whole friend group:
tomoyo_print_bprm(9)tomoyo_filetype(9)tomoyo_init_log(9)tomoyo_get_audit(9)tomoyo_write_log2(9)tomoyo_write_log(9)tomoyo_read_log(9)tomoyo_poll_log(9)
and that's the page!! π this whole thing lives in ./security/tomoyo, the source is ./security/tomoyo, and it's dated October 2026 β so yeah, mark your calendars bestie, future vibes only βππ¦
π¦ 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