svc_tcp_handshake_done(9)

📦 version 7.3.1, in nixpkgs unstable

💅 svc_tcp_handshake_done(9) — from the Kernel API Manual, bestie ✨

okay so picture this: it's the kernel API manual, section 9, and the star of the show is svc_tcp_handshake_done — say it with me, we're learning today 🎀

🌸 NAME 🌸

svc_tcp_handshake_done — the handshake completion handler 💖 like it literally handles what happens when the handshake is done, no cap

✨ SYNOPSIS ✨

void svc_tcp_handshake_done (void *data , int status , key_serial_t
peerid );

that's it, that's the whole vibe check — void return, three args, she's serving function signature realness 👑

🦋 ARGUMENTS 🦋

  • data — the address of the xprt to wake 🌈 lowkey it's just here to get woken up, let her sleep
  • status — the status of the handshake 🫶 how'd it go? this tea right here
  • peerid — the serial number of the key containing the remote peer's identity 🔑 iykyk, it's giving very main character identity energy

💜 DESCRIPTION 💜

okay so here's the situation, bestie 😭 if a security policy is specified as an export option, we don't have a specific export here to check. like, none. zero. it's not in the building 🙈

so instead?? we set a "TLS session is present" flag on the xprt — literally just flag it and move on — and then we let an upper layer enforce the local security policy 👑 delegation!! we love to see it. she's not doing the security check herself, she's letting the upper layer be the main character 💅

ngl the whole point is: no specific export to check → set the flag → upper layer handles enforcement. periodt. 🔥

🍓 SEE ALSO 🍓

so the kernel file is ./net/sunrpc/svcsock.c and honestly there's a whole friend group here, go say hi 🫶

like that's the whole group chat, every single one of them, we didn't skip a single bestie 💖

and that's the page!! brought to you by ./net/sunrpc, dated October 2026, living in section 9 of the Kernel API Manual — svc_tcp_handshake_done(9) fr fr ⭐ slay, go read the source, mwah 💋🧚

📦 where this page comes from