tomoyo_check_acl(9)

💅 tomoyo_check_acl(9) 💅

okay so this is the Kernel API Manual page for tomoyo_check_acl(9), and we are literally so back, bestie. 🫶

✨ NAME ✨

tomoyo_check_acl — do permission check. That's the whole vibe, no cap. 💖

🦋 SYNOPSIS 🦋

void tomoyo_check_acl (struct tomoyo_request_info *r , bool
       (*check_entry)(struct tomoyo_request_info *, const struct
       tomoyo_acl_info *) );

🎀 ARGUMENTS 🎀

• r — pointer to struct tomoyo_request_info. It's giving "request info main character energy." 👑
• check_entry — callback function to check type specific parameters. This is the little helper that does the type-specific vibe check. ✨

🔥 DESCRIPTION 🔥

Return situation: 0 on success, and a negative value otherwise. That's the return story, fr fr. 💯

Caller holds tomoyo_read_lock. This is important, bestie — the manual says it plainly, so keep that lock energy in mind. 🔒💅

🌈 SEE ALSO 🌈

The kernel file ./security/tomoyo/domain.c is the file mentioned here, and it's also giving these SEE ALSO besties. All of them are staying, periodt:

• tomoyo_update_policy(9)
• tomoyo_same_acl_head(9)
• tomoyo_update_domain(9)
• tomoyo_last_word(9)
• tomoyo_same_transition_control(9)
• tomoyo_write_transition_control(9)
• tomoyo_scan_transition(9)
• tomoyo_transition_type(9)
• tomoyo_same_aggregator(9)
• tomoyo_write_aggregator(9)
• tomoyo_find_namespace(9)
• tomoyo_assign_namespace(9)
• tomoyo_namespace_jump(9)
• tomoyo_assign_domain(9)
• tomoyo_environ(9)
• tomoyo_find_next_domain(9)
• tomoyo_dump_page(9)

mwah 💋 — this one came from ./security/tomoyo, dated October 2026, and it's literally the tomoyo_check_acl(9) page. byeee, go hold that tomoyo_read_lock with main character energy 🫶✨🌸