tomoyo_socket_sendmsg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to tomoyo_socket_sendmsg from the Kernel API Manual β€” it's a little permission-check moment with main-character energy, and we're gonna read it together, no cap 🫢✨

🌸 NAME 🌸

tomoyo_socket_sendmsg β€” check permission for sendmsg(). That's the whole assignment, periodt πŸ’…

✨ SYNOPSIS ✨

int tomoyo_socket_sendmsg (struct socket *sock , struct msghdr *msg ,
int size );

πŸŽ€ ARGUMENTS πŸŽ€

  • sock β€” a pointer to struct socket; the original literally says "struct socket", so yeah, that's the vibe πŸ’–
  • msg β€” a pointer to struct msghdr; original says "struct msghdr", slay πŸ¦‹
  • size β€” size of message. That's it. That's the number πŸ”₯

πŸ’– DESCRIPTION πŸ’–

It returns 0 on success, negative value otherwise. That's the whole plot β€” no plot twists, just return-code honesty πŸ˜ŒπŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./security/tomoyo/tomoyo.c is the spot, and the whole squad is: 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_symlink(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_task_alloc(9), tomoyo_task_free(9), tomoyo_init(9). Literally all of them, iykyk πŸ’œ


okay bye bestie 🫢 the source/version footer bit is ./security/tomoyo, the date is October 2026, and the manual tag is tomoyo_socket_sendmsg(9) β€” mwah πŸ’‹πŸŒˆ

πŸ“¦ where this page comes from