xprt_lookup_rqst(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xprt_lookup_rqst β€” the Kernel API Manual girlie's guide ✨

okay so picture this: you're deep in the Kernel API Manual, right, and you need to find the RPC request that matches an XID. that's it. that's the whole vibe. this function is the friend who knows exactly who's who in the group chat πŸ’–


🌸 NAME 🌸

xprt_lookup_rqst β€” bestie's whole job is finding an RPC request corresponding to an XID. literally that. no cap πŸŽ€


✨ SYNOPSIS ✨

struct rpc_rqst * xprt_lookup_rqst (struct rpc_xprt *xprt , __be32 xid
);

like, she takes an xprt and an xid, and hands you back a struct rpc_rqst *. iconic signature tbh 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • xprt β€” the transport on which the original request was transmitted. yes, that transport. the one that sent the thing πŸ’…
  • xid β€” the RPC XID of the incoming reply. the little name tag that says "hi i'm the reply you're looking for" 🌈

πŸ‘‘ DESCRIPTION πŸ‘‘

Caller holds xprt->queue_lock. periodt. no exceptions, no "oops i forgot", the lock is yours to hold before you call her, mwah πŸ’œ

that's genuinely the whole description and honestly? she said what she said. short, sweet, and absolutely non-negotiable β€” the way that a function can just have ONE rule and still be main character energy 😭πŸ”₯


⭐ SEE ALSO ⭐

okay bestie, buckle up, because the family tree is LONG and every single one of these is invited to the party 🧚✨ source of truth is the kernel file ./net/sunrpc/xprt.c and here's everyone:

like i said. LONG. but we love a rich extended universe πŸ’€πŸ’–


anyway that's the page bestie, and before you go β€” this little masterpiece lives in the source directory ./net/sunrpc and it's dated October 2026, so mark your calendars accordingly, drink some water, hold that xprt->queue_lock, and slay πŸŒΈπŸ¦‹πŸ’…βœ¨

πŸ“¦ where this page comes from