tomoyo_supervisor(9)
Bestie, welcome to tomoyo_supervisor(9) from the Kernel API Manual β the page where we ask for the supervisor's decision, and itβs giving important little kernel moment energy π
β¨
πΈ NAME πΈ
tomoyo_supervisor β ask for the supervisor's decision. Thatβs the name, thatβs the vibe, no cap π«Ά.
β¨ SYNOPSIS β¨
int tomoyo_supervisor (struct tomoyo_request_info *r , const char *fmt ,
... );
π ARGUMENTS π
rβ pointer tostruct tomoyo_request_info. Yes, that exact struct, periodt.fmtβ theprintf's format string, followed by parameters....β variable arguments.
π DESCRIPTION π
Okay so the return-value tea is wild but simple: it returns 0 if the supervisor decided to permit the access request which violated the policy in enforcing mode. It returns TOMOYO_RETRY_REQUEST if the supervisor decided to retry the access request which violated the policy in enforcing mode. It returns 0 if it is not in enforcing mode. Otherwise, it returns -EPERM.
Thatβs the whole decision menu β permit, retry, not enforcing, or -EPERM β and yes, the two 0 cases are both real, so read the conditions carefully bestie π.
π¦ SEE ALSO π¦
Kernel file ./security/tomoyo/common.c is the main character here, and these are all the besties it points you to:
tomoyo_addprintf(9)tomoyo_flush(9)tomoyo_set_string(9)tomoyo_io_printf(9)tomoyo_set_space(9)tomoyo_set_lf(9)tomoyo_set_slash(9)tomoyo_init_policy_namespace(9)tomoyo_print_namespace(9)tomoyo_print_name_union(9)tomoyo_print_name_union_quoted(9)tomoyo_print_number_union_nospace(9)tomoyo_print_number_union(9)tomoyo_assign_profile(9)tomoyo_profile(9)tomoyo_find_yesno(9)tomoyo_set_uint(9)tomoyo_set_mode(9)tomoyo_write_profile(9)tomoyo_print_config(9)tomoyo_read_profile(9)tomoyo_same_manager(9)tomoyo_update_manager_entry(9)tomoyo_write_manager(9)tomoyo_read_manager(9)tomoyo_manager(9)tomoyo_select_domain(9)tomoyo_same_task_acl(9)tomoyo_write_task(9)tomoyo_delete_domain(9)tomoyo_write_domain2(9)tomoyo_write_domain(9)tomoyo_print_condition(9)tomoyo_set_group(9)tomoyo_print_entry(9)tomoyo_read_domain2(9)tomoyo_read_domain(9)tomoyo_write_pid(9)tomoyo_read_pid(9)tomoyo_write_exception(9)tomoyo_read_group(9)tomoyo_read_policy(9)tomoyo_read_exception(9)tomoyo_truncate(9)tomoyo_numscan(9)tomoyo_patternize_path(9)tomoyo_add_entry(9)tomoyo_find_domain_by_qid(9)tomoyo_poll_query(9)tomoyo_read_query(9)tomoyo_write_answer(9)tomoyo_read_version(9)tomoyo_update_stat(9)tomoyo_read_stat(9)tomoyo_write_stat(9)tomoyo_open_control(9)tomoyo_poll_control(9)tomoyo_set_namespace_cursor(9)tomoyo_has_more_namespace(9)tomoyo_read_control(9)tomoyo_parse_policy(9)tomoyo_write_control(9)tomoyo_close_control(9)tomoyo_check_profile(9)tomoyo_load_builtin_policy(9)
And thatβs the page, bestie! Source/version, date, and manual name, all present and accounted for: ./security/tomoyo, October 2026, tomoyo_supervisor(9) ππ«Άβ¨
π¦ 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