svc_xprt_received(9)

📦 version 7.3.1, in nixpkgs unstable

okay bestie, you just opened svc_xprt_received(9) from the Kernel API Manual, and lowkey this one is short but the rules are rules 💅

🎀 NAME 🎀

svc_xprt_received — start next receiver thread

✨ SYNOPSIS ✨

Here's the whole signature, character-for-character, no edits:

void svc_xprt_received (struct svc_xprt *xprt );

🦋 ARGUMENTS 🦋

  • xprt — controlling transport. That's the transport you're working with, bestie.

💖 DESCRIPTION 💖

The caller must hold the XPT_BUSY bit. And after that? The caller must not thereafter touch transport data. Like, hands off the transport data — do not touch it. 🫶

It's giving "start the next receiver thread," and the caller has to have the XPT_BUSY bit first. Periodt. ✨

🔥 NOTE 🔥

Okay, key lil' detail: XPT_DATA only gets cleared when a read-attempt finds no (or insufficient) data. That's the whole note — no cap. 💀

🌈 SEE ALSO 🌈

Kernel file: ./net/sunrpc/svc_xprt.c

mwah 💋 shoutout to the source/version line: ./net/sunrpc, dated October 2026 — catch you in the kernel, bestie! 🌈✨

📦 where this page comes from