PROBE::SOCKET.READ(3stap)

πŸ’– probe::socket.readv.return β€” a Socket Tapset moment πŸ’–

okay bestie, welcome to the PROBE::SOCKET.READ page from the Socket Tapset β€” yes that's the manual name, we're folding it in right here at the top like a lil name tag πŸŽ€


✨ NAME ✨

probe::socket.readv.return β€” it's giving conclusion of receiving a message via sock_readv πŸ¦‹


✨ SYNOPSIS ✨

probe socket.readv.return {}

that's it. that's the whole vibe. no args, just vibes 🫢


✨ VALUES ✨

these are the lil goodies you get handed inside the probe, and ngl every single one of them is important:

  • type β€” the socket type value πŸ”₯
  • name β€” the name of this probe, i.e. its whole identity, main character energy πŸ‘‘
  • protocol β€” the protocol value
  • state β€” the socket state value
  • flags β€” the socket flags value
  • size β€” size of the message that got received, in bytes β€” OR the error code if success = 0 (so like, check success first bestie, don't be out here reading an error code as a byte count 😭)
  • family β€” the protocol family value
  • success β€” was the receive successful? 1 = yes, 0 = no. iconic binary behaviour πŸ’…

✨ CONTEXT ✨

the message receiver. that's who's on stage here πŸ’œ


✨ DESCRIPTION ✨

so literally: this probe fires at the conclusion of receiving a message on a socket via the sock_readv function ✨ like it's the after-party of the readv, the credits rolling, the "we did it joe" moment πŸŽ€


✨ SEE ALSO ✨

  • tapset::socket(3stap) β€” go read that one too, bestie, it's the whole socket tapset and it eats πŸ’…

and that's the page!! this was the SystemTap Tapset Reference β€” the version line was being a lil shy and got truncated to just Ver, but the date is September 2026 fr fr. thanks for reading, ily, go probe some sockets πŸ¦‹πŸ’–βœ¨

πŸ“¦ where this page comes from