tomoyo_scan_transition(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tomoyo_scan_transition β€” a lil peek inside the Kernel API Manual (section 9, bestie, kernel-land) πŸŽ€

okay so picture this: you're deep in TOMOYO land and you need to figure out whether a specific domain transition type is even in the building. That's this function. It's giving "bouncer at the club checking the list" energy πŸ”₯


✨ NAME ✨

tomoyo_scan_transition β€” literally just tryna find one specific domain transition type. That's it. That's the whole job. πŸ’…


🌸 SYNOPSIS 🌸

bool tomoyo_scan_transition (const struct list_head *list , const struct
tomoyo_path_info *domainname , const struct tomoyo_path_info *program ,
const char *last_name , const enum tomoyo_transition_type type );

no cap, that's the signature. copy it exactly, she's sensitive 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • list β€” Pointer to struct list_head. yes bestie the actual list we're rummaging through 🧚
  • domainname β€” The name of current domain. like, where we are right now ✨
  • program β€” The name of requested program. the one we're looking for πŸ‘€
  • last_name β€” The last component of domainname. just the tail end of it, iykyk πŸ’œ
  • type β€” One of values in enum tomoyo_transition_type. pick your fighter from the enum 🌈

πŸ’– DESCRIPTION πŸ’–

Returns true if found one, false otherwise. boom. that's the whole vibe check βœ…βŒ

Caller holds tomoyo_read_lock. like β€” not optional, bestie, you gotta be holding it already. don't come in here empty-handed πŸ˜­πŸ”’


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./security/tomoyo/domain.c β€” and honestly the whole friend group shows up here:

like, the entire squad πŸ’€πŸ‘―β€β™€οΈ go read all of them fr fr.


ok that's the page!! sourced straight from ./security/tomoyo, dated October 2026, and she lives at tomoyo_scan_transition(9) πŸŽ€βœ¨ mwah, go read some kernel code bestie, you got this πŸ’–πŸ¦‹
πŸ“¦ where this page comes from