tomoyo_check...n_permission(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ tomoyo_check_open_permission(9) ✨

okay bestie, welcome to the Kernel API Manual β€” this page is all about one lil permission check, and it's giving security-core energy. no cap. πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

int tomoyo_check_open_permission (struct tomoyo_domain_info *domain ,
const struct path *path , const int flag );

πŸ’– ARGUMENTS πŸ’–

  • domain β€” Pointer to struct tomoyo_domain_info. like, the domain info struct, okay?
  • path β€” Pointer to struct path. the path, obviously, slay.
  • flag β€” Flags for open. open flags, periodt.

🌸 DESCRIPTION 🌸

Returns 0 on success, negative value otherwise. that's it, that's the whole vibe. success gets a 0, anything else is negative β€” so if you see a negative number, it's not slaying. 😭

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./security/tomoyo/file.c β€” and the whole function squad: 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_same_path_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_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).


mwah πŸ’‹ this page is from ./security/tomoyo and dated October 2026 β€” go check those permissions, bestie, and stay iconic. periodt.

πŸ“¦ where this page comes from