nlm4svc_proc_granted_msg(9)

💅 nlm4svc_proc_granted_msg(9) — the Kernel API Manual moment ✨

okay bestie, gather round, because this page is lowkey iconic and it's giving “blocked lock finally got its moment.” 🎀

🌸 NAME 🌸

nlm4svc_proc_granted_msg — GRANTED_MSG: Blocked lock has been granted. That's the whole assignment, and it ate. 💖

✨ SYNOPSIS ✨

__be32 nlm4svc_proc_granted_msg (struct svc_rqst *rqstp );

boom, that's the signature, no cap. 🫶

🎀 ARGUMENTS 🎀

• rqstp — the RPC transaction context. like, it's the backstage pass for the whole call. 🎟️

💅 RETURN 💅

• rpc_success: RPC executed successfully. slay. ✅
• rpc_system_err: RPC execution failed. not slay, but very important. 💀

🦋 DESCRIPTION 🦋

RPC synopsis: void NLMPROC4_GRANTED_MSG(nlm4_testargs) = 10;

The response to this request is delivered via the GRANTED_RES procedure. so yeah, the answer comes back through GRANTED_RES — that's the vibe, iykyk. 🫶

🌈 SEE ALSO 🌈

Kernel file ./fs/lockd/svc4proc.c is the home base, and then we have the whole friend group:

• nlm4svc_proc_null(9)
• nlm4svc_proc_test(9)
• nlm4svc_proc_lock(9)
• nlm4svc_proc_cancel(9)
• nlm4svc_proc_unlock(9)
• nlm4svc_proc_granted(9)
• nlm4svc_proc_test_msg(9)
• nlm4svc_proc_lock_msg(9)
• nlm4svc_proc_cancel_msg(9)
• nlm4svc_proc_unlock_msg(9)
• nlm4svc_proc_granted_res(9)
• nlm4svc_proc_sm_notify(9)
• nlm4svc_proc_unused(9)
• nlm4svc_proc_share(9)
• nlm4svc_proc_unshare(9)
• nlm4svc_proc_nm_lock(9)
• nlm4svc_proc_free_all(9)

---

🫶 source/version: ./fs/lockd; date: October 2026; page: nlm4svc_proc_granted_msg(9) — that's the tea, bye bestie! 💖