tomoyo_init_log(9)

💖 tomoyo_init_log(9) 💖

Welcome to the Kernel API Manual, bestie — today’s main character is tomoyo_init_log(9), and it’s here to allocate a buffer for audit logs. Periodt. ✨

🌸 NAME 🌸

tomoyo_init_log — allocate buffer for audit logs. That’s literally the whole vibe. 💅

🦋 SYNOPSIS 🦋

char * tomoyo_init_log (struct tomoyo_request_info *r , int len , const
       char *fmt , va_list args );

🎀 ARGUMENTS 🎀

• r — pointer to struct tomoyo_request_info. Your request-info bestie. 🫶
• len — buffer size needed for fmt and args. Get those numbers right, okay? 😭
• fmt — the printf’s format string. Iconic formatting behavior. ⭐
• args — va_list structure for fmt. The whole variadic situation. 💜

🌈 DESCRIPTION 🌈

It returns a pointer to allocated memory. Slay. ✨

This function uses kzalloc, so the caller must kfree if this function didn’t return NULL. No cap: that’s your memory to clean up, bestie — don’t leave it hanging. 💅🔥

Lowkey important: kzalloc is in the building, so the kfree rule is real. If this function didn’t return NULL, caller cleanup is mandatory.

👑 SEE ALSO 👑

Kernel file ./security/tomoyo/audit.c plus these absolute icons:

• tomoyo_print_bprm(9)
• tomoyo_filetype(9)
• tomoyo_print_header(9)
• tomoyo_get_audit(9)
• tomoyo_write_log2(9)
• tomoyo_write_log(9)
• tomoyo_read_log(9)
• tomoyo_poll_log(9)

Okay bye bestie — shoutout to source ./security/tomoyo, dated October 2026, and this page is tomoyo_init_log(9) 💖🎀🦋