tomoyo_path_symlink(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

tomoyo_path_symlink β€” the target for security_path_symlink(). πŸ’… And yes bestie, this is tomoyo_path_symlink(9) from the Kernel API Manual β€” we are so in the right place. πŸ¦‹


πŸ“œ SYNOPSIS πŸ“œ

int tomoyo_path_symlink (const struct path *parent , struct dentry
       *dentry , const char *old_name );

That's the whole signature, character-for-character, no cap.


🧩 ARGUMENTS 🧩

  • parent β€” pointer to "struct path". 🫢
  • dentry β€” pointer to "struct dentry". πŸ¦‹
  • old_name β€” Symlink's content. πŸŽ€

πŸ’– DESCRIPTION πŸ’–

Returns 0 on success, negative value otherwise. That's the whole vibe check: 0 = slay, negative = not slay. 😭 No extra lore, just those facts.


🌈 SEE ALSO 🌈

Kernel file ./security/tomoyo/tomoyo.c is in the group chat, along with: tomoyo_domain(9), tomoyo_cred_prepare(9), tomoyo_bprm_committed_creds(9), tomoyo_bprm_creds_for_exec(9), tomoyo_bprm_check_security(9), tomoyo_inode_getattr(9), tomoyo_path_truncate(9), tomoyo_file_truncate(9), tomoyo_path_unlink(9), tomoyo_path_mkdir(9), tomoyo_path_rmdir(9), tomoyo_path_mknod(9), tomoyo_path_link(9), tomoyo_path_rename(9), tomoyo_file_fcntl(9), tomoyo_file_open(9), tomoyo_file_ioctl(9), tomoyo_path_chmod(9), tomoyo_path_chown(9), tomoyo_path_chroot(9), tomoyo_sb_mount(9), tomoyo_sb_umount(9), tomoyo_sb_pivotroot(9), tomoyo_socket_listen(9), tomoyo_socket_connect(9), tomoyo_socket_bind(9), tomoyo_socket_sendmsg(9), tomoyo_task_alloc(9), tomoyo_task_free(9), tomoyo_init(9). All invited, all iconic. πŸ‘‘

Sign-off: from ./security/tomoyo (the source/version corner), dated October 2026, this was tomoyo_path_symlink(9). Mwah. πŸ’–πŸŽ€

πŸ“¦ where this page comes from