tomoyo_write_domain2(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to tomoyo_write_domain2(9) from the Kernel API Manual πŸ’– she’s the domain-policy-writing girlie and this is her page. Let’s get into it, no cap. ✨

πŸŽ€ NAME πŸŽ€

tomoyo_write_domain2 β€” write domain policy. That’s the whole vibe, periodt. πŸ’…

✨ SYNOPSIS ✨

Here’s the exact signature, untouched and iconic:

int tomoyo_write_domain2 (struct tomoyo_policy_namespace *ns , struct list_head *list , char *data , const bool is_delete );

🌸 ARGUMENTS 🌸

  • ns β€” pointer to struct tomoyo_policy_namespace. Like, literally that pointer. 🫢
  • list β€” pointer to struct list_head. Yes bestie, that exact struct. πŸ’–
  • data β€” the policy to be interpreted. She’s the actual policy content in the chat. πŸ‘€
  • is_delete β€” True if it is a delete request. Delete-request energy only, iykyk. πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

Returns 0 on success, negative value otherwise. That’s the return tea β˜• β€” success gets 0, and otherwise gets a negative value.

Caller holds tomoyo_read_lock. No cap, that’s the context note β€” the caller is the one holding tomoyo_read_lock. πŸ”’

πŸ‘‘ SEE ALSO πŸ‘‘

These are the related (9) entries, and we are keeping every single one β€” no skips, bestie. πŸ’–


πŸ’– source/version: ./security/tomoyo β€’ date: October 2026 β€’ title: tomoyo_write_domain2(9) β€’ from the Kernel API Manual β€’ bye bestie, slay that policy! πŸ’…

πŸ“¦ where this page comes from