tomoyo_same_path_acl(9)

🌸 NAME 🌸

okay so bestie, this is tomoyo_same_path_acl(9), and yes it’s from the Kernel API Manual. Its whole gig? Check for duplicated struct tomoyo_path_acl entry. That’s the assignment, and it ate. 💅

✨ SYNOPSIS ✨

bool tomoyo_same_path_acl (const struct tomoyo_acl_info *a , const struct tomoyo_acl_info *b );

No cap, that’s the signature. 🫶

🎀 ARGUMENTS 🎀

• a — pointer to struct tomoyo_acl_info. It’s giving “first ACL info pointer” energy. ✨
• b — pointer to struct tomoyo_acl_info. Matching pointer-to-ACL-info vibe, bestie. 💖

💖 DESCRIPTION 💖

Returns true if a == b except permission bits, false otherwise. That’s the whole plot. periodt. 👑

🦋 SEE ALSO 🦋

Kernel file ./security/tomoyo/file.c is right here, and the whole crew is:

• tomoyo_put_name_union(9)
• tomoyo_compare_name_union(9)
• tomoyo_put_number_union(9)
• tomoyo_compare_number_union(9)
• tomoyo_add_slash(9)
• tomoyo_get_realpath(9)
• tomoyo_audit_path_log(9)
• tomoyo_audit_path2_log(9)
• tomoyo_audit_mkdev_log(9)
• tomoyo_audit_path_number_log(9)
• tomoyo_check_path_acl(9)
• tomoyo_check_path_number_acl(9)
• tomoyo_check_path2_acl(9)
• tomoyo_check_mkdev_acl(9)
• tomoyo_merge_path_acl(9)
• tomoyo_update_path_acl(9)
• tomoyo_same_mkdev_acl(9)
• tomoyo_merge_mkdev_acl(9)
• tomoyo_update_mkdev_acl(9)
• tomoyo_same_path2_acl(9)
• tomoyo_merge_path2_acl(9)
• tomoyo_update_path2_acl(9)
• tomoyo_path_permission(9)
• tomoyo_execute_permission(9)
• tomoyo_same_path_number_acl(9)
• tomoyo_merge_path_number_acl(9)
• tomoyo_update_path_number_acl(9)
• tomoyo_path_number_perm(9)
• tomoyo_check_open_permission(9)
• tomoyo_path_perm(9)
• tomoyo_mkdev_perm(9)
• tomoyo_path2_perm(9)
• tomoyo_same_mount_acl(9)
• tomoyo_update_mount_acl(9)
• tomoyo_write_file(9)

that’s the tea 🫶 source/version is ./security/tomoyo, date is October 2026, and the page is tomoyo_same_path_acl(9). mwah 💋