nfsd41_cb_referring_call(9)
π 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:
- Kernel file
./fs/nfsd/nfs4callback.cβ the source herself π nfsd41_cb_destroy_referring_call_list(9)β the cleanup arc π§Ήnfsd4_run_cb(9)β the running arc πββοΈnfsd_net_cb_shutdown(9)β the shutting-down arc π»nfsd_net_cb_init(9)β the starting-fresh arc π±
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms