sock_recvmsg(9)
π sock_recvmsg(9) β from the Kernel API Manual, bestie π
okay so picture this: it's a kernel API manual page, it's called sock_recvmsg(9), and it's literally about catching messages on a socket. i got you. let's go π«Ά
β¨ NAME β¨
sock_recvmsg β receive a message from @sock π
(yes the @ is in the original, it's giving very "i'm addressing the socket directly")
πΈ SYNOPSIS πΈ
int sock_recvmsg (struct socket *sock , struct msghdr *msg , int flags
);
three args, one int out, no cap. π
π¦ ARGUMENTS π¦
sockβ socket πmsgβ message to receive πΈflagsβ message flags β
that's the whole lineup, bestie. no hidden extras, i checked.
π₯ DESCRIPTION π₯
so what it does: it receives msg from sock, passing through LSM. π
and what it gives back? the total number of bytes received, or an error. that's it. that's the whole vibe check. π
lowkey important: "or an error" is doing a LOT of work in that sentence β always check your return value, bestie, don't just assume the bytes arrived. π
π SEE ALSO π
the kernel file is ./net/socket.c and honestly the friend group here is HUGE, so buckle up π§:
move_addr_to_kernel(9)move_addr_to_user(9)sock_read_xattr(9)sock_alloc_file(9)sock_from_file(9)sockfd_lookup(9)sock_alloc(9)sock_release(9)sock_sendmsg(9)kernel_sendmsg(9)kernel_recvmsg(9)sock_create_lite(9)__sock_create(9)sock_create(9)sock_create_kern(9)sock_register(9)sock_unregister(9)kernel_bind(9)kernel_listen(9)kernel_accept(9)kernel_connect(9)kernel_getsockname(9)kernel_getpeername(9)kernel_sock_shutdown(9)kernel_sock_ip_overhead(9)
like i said. entire friend group. all iconic, all in the group chat. π
and that's the page!! π this little cutie comes from ./net, dated October 2026, and the header on it was sock_recvmsg(9) from the Kernel API Manual β mwah, slay, periodt. π
β¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms