tomoyo_update_domain(9)

📦 version 7.3.1, in nixpkgs unstable

💖 tomoyo_update_domain 💖

okay so bestie, you know how the kernel has this whole security module situation going on? this is one of those internal functions from the TOMOYO Linux security module — it lives in the kernel API, no cap. it's all about updating an entry for domain policy. let me break it down for you.

✨ SYNOPSIS ✨

int tomoyo_update_domain (struct tomoyo_acl_info *new_entry , const int
       size , struct tomoyo_acl_param *param , bool (*check_duplicate)(const
       struct tomoyo_acl_info *, const struct tomoyo_acl_info *) , bool
       (*merge_duplicate)(struct tomoyo_acl_info *, struct tomoyo_acl_info *,
       const bool) );

🎀 ARGUMENTS 🎀

  • new_entry — a pointer to struct tomoyo_acl_info. this is the shiny new entry you're trying to slide into the policy, bestie.
  • size — the size of new_entry, in bytes. like, how much space your new entry is taking up fr fr.
  • param — a pointer to struct tomoyo_acl_param. parameters for the operation, iykyk.
  • check_duplicate — a callback function to find a duplicated entry. think of it as a little detective that hunts for dupes 👀
  • merge_duplicate — a callback function to merge a duplicated entry. so if there is a dupe, this one handles combining them. iconic behaviour honestly 💅

🦋 DESCRIPTION 🦋

returns 0 on success, and a negative value otherwise. that's the whole vibe check — zero means we ate, negative means something went sideways.

important bestie: the caller holds tomoyo_read_lock. so like, don't go calling this without that lock situation sorted, okay? periodt.

🌸 SEE ALSO 🌸

the whole squad, in the kernel file ./security/tomoyo/domain.c:

💫 and that's the whole thing, bestie 💫 go off and update those domain policies. this page is from the ./security/tomoyo section of the kernel API manual, dated October 2026 — so you know it's fresh 🌈✨ mwah 💋

📦 where this page comes from