tipc_recvstream(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tipc_recvstream(9) β€” the kernel API manual, but make it make sense πŸŽ€

okay so bestie, this is tipc_recvstream from the kernel API manual, and it's literally the one that pulls actual stream data out. no cap. let's go ✨


🌸 NAME 🌸

tipc_recvstream β€” receive stream-oriented data πŸ’– (yes that's the whole name, she's straightforward and we respect it)


πŸ¦‹ SYNOPSIS πŸ¦‹

int tipc_recvstream (struct socket *sock , struct msghdr *m , size_t
buflen , int flags );

✨ ARGUMENTS ✨

  • sock β€” the network socket, aka the whole vibe connection itself 🫢
  • m β€” descriptor for message info, the little info card about the message
  • buflen β€” total size of user buffer area, like how much room you've cleared in your bag πŸ‘œ
  • flags β€” receive flags, the options-y bits

πŸ’œ DESCRIPTION πŸ’œ

so this one is used for SOCK_STREAM messages only β€” that's the whole assignment, she does not moonlight. no cap. 🌈

if there isn't enough data available, she will optionally wait for more β€” patient queen energy πŸ‘‘ β€” and she never truncates data. nope. not ever. she would never do that to you. πŸ’…


πŸ”₯ RETURN πŸ”₯

size of returned message data, or errno otherwise 😭 (if it goes sideways you get an errno, that's the deal)


πŸŽ€ SEE ALSO πŸŽ€

this is the friend group. the whole squad. literally all of them ⭐

Kernel file ./net/tipc/socket.c and:


ngl that's a big squad but every single one of them is in the group chat, iykyk 🧚

okay that's the whole page, mwah πŸ’‹ β€” this came out of ./net/tipc, dated October 2026, and it's your girl tipc_recvstream(9) signing off. slay, stay safe in the receive path, and don't truncate anything on your way out πŸ’–βœ¨πŸ“

πŸ“¦ where this page comes from