nfsd41_cb_d...ng_call_list(9)

✨ NAME ✨

nfsd41_cb_destroy_referring_call_list — bestie, this is the one that releases your referring call info 🎀 it's the cleanup crew, the "you're done here, go home" of callback land, from the Kernel API Manual (section 9 ofc, iykyk) 💅

---

🌸 SYNOPSIS 🌸

void nfsd41_cb_destroy_referring_call_list(struct nfsd4_callback *cb);

Lowkey the whole signature is just that one line, no cap. ✨

---

🦋 ARGUMENTS 🦋

• cb — the context of a callback that has completed, periodt. That's it, that's the whole vibe — she's done, she's finished, she's ready to be let go 🫶

---

💖 DESCRIPTION 💖

okay so listen 👑 if you're the kind of caller who allocated referring calls using nfsd41_cb_referring_call, you literally must release those resources by calling nfsd41_cb_destroy_referring_call_list. No skipping, no ghosting your own memory, that's not the move 😭 your resources are your responsibility bestie, take them to their little farewell party 🎀

Also, real talk — the caller serializes access to cb 🔥 that's on you, not on this function. So make sure you've got that handled before you call in, okurrr? 💅

ngl this is a "clean up after yourself" situation and the vibes are extremely main character energy 🌈 do not leave your referring calls hanging out there with no release, it's giving leak behavior and we don't do that 🙈

---

⭐ SEE ALSO ⭐

• Kernel file ./fs/nfsd/nfs4callback.c
• nfsd41_cb_referring_call(9)
• nfsd4_run_cb(9)
• nfsd_net_cb_shutdown(9)
• nfsd_net_cb_init(9)

like, go read those too, they're all in the same little friend group bestie 🧚💜

---

and that's the whole page fr fr — with love from ./fs/nfsd, dated October 2026 🌸💅 this fairy godmother of callback cleanup says bye, mwah 🫶✨