tomoyo_supervisor(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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 to struct tomoyo_request_info. Yes, that exact struct, periodt.
  • fmt β€” the printf'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:


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