nfsd41_cb_referring_call(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– nfsd41_cb_referring_call(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so picture this: you're deep in the kernel, NFSv4.1 callback land, and someone needs a referring call attached to a callback op. that's this function. welcome to the group chat, it's the Kernel API Manual and we're all gonna understand it together πŸ’…


✨ SYNOPSIS ✨

void nfsd41_cb_referring_call (struct nfsd4_callback *cb ,
                               struct nfs4_sessionid *sessionid ,
                               u32 slotid ,
                               u32 seqno );

that's it. that's the whole vibe. four args, returns void, no drama 🌸


🫢 ARGUMENTS 🫢

  • cb β€” the context of the callback you're adding the rc to. like, this is the callback, the main character πŸ‘‘
  • sessionid β€” the referring call's session ID. yep, the session's very own ID πŸ¦‹
  • slotid β€” the referring call's session slot index. which slot, bestie? this one πŸ”₯
  • seqno β€” the referring call's slot sequence number. the seqno of that slot, fr fr ⭐

πŸ’œ DESCRIPTION πŸ’œ

so here's what's tea: the caller serializes access to cb. that's on you, not on this function. you handle the locking, it just does the add. periodt πŸ™ˆ

NB: if memory allocation fails, the referring call is NOT added. 😭 like literally it just doesn't happen. no rc for you. check your allocation situation, bestie, this is important πŸ’€

🌈 SEE ALSO 🌈

the lore continues over here, go read these:


kisses from ./fs/nfsd β€” this page was served fresh in October 2026 and the whole thing is filed under nfsd41_cb_referring_call(9). slay, go forth and add those referring calls πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from