nlmsvc_proc_unlock(9)

💅 NAME 💅

okay so this is nlmsvc_proc_unlock(9) from the Kernel API Manual, and the function is nlmsvc_proc_unlock — UNLOCK: Remove a lock. It’s giving “lock says bye bestie” energy, and we’re here for it.

---

✨ SYNOPSIS ✨

__be32 nlmsvc_proc_unlock (struct svc_rqst *rqstp );

🎀 ARGUMENTS 🎀

• rqstp — RPC transaction context. That’s the whole RPC moment wrapped up, iykyk.

🫶 RETURN 🫶

• rpc_success: RPC executed successfully. Slay, it worked.
• rpc_drop_reply: Do not send an RPC reply. Literally no reply, periodt.

🌸 DESCRIPTION 🌸

RPC synopsis:

nlm_res NLM_UNLOCK(nlm_unlockargs) = 4;

The permissible procedure status codes are:

• LCK_GRANTED: The requested lock was released. Iconic — the lock is gone 👋.
• LCK_DENIED_GRACE_PERIOD: The server has recently restarted and is re-establishing existing locks, and is not yet ready to accept normal service requests. It’s giving “give me a sec, I’m rebuilding my whole situation” energy.

The Linux NLM server implementation also returns:

• LCK_DENIED_NOLOCKS: A needed resource could not be allocated. Not the resource allocation failing 😭.

🦋 SEE ALSO 🦋

Kernel file ./fs/lockd/svcproc.c plus the whole lockd bestie lineup:

• nlmsvc_proc_null(9)
• nlmsvc_proc_test(9)
• nlmsvc_proc_lock(9)
• nlmsvc_proc_cancel(9)
• nlmsvc_proc_granted(9)
• nlmsvc_proc_test_msg(9)
• nlmsvc_proc_lock_msg(9)
• nlmsvc_proc_cancel_msg(9)
• nlmsvc_proc_unlock_msg(9)
• nlmsvc_proc_granted_msg(9)
• nlmsvc_proc_granted_res(9)
• nlmsvc_proc_sm_notify(9)
• nlmsvc_proc_unused(9)
• nlmsvc_proc_share(9)
• nlmsvc_proc_unshare(9)
• nlmsvc_proc_nm_lock(9)
• nlmsvc_proc_free_all(9)

---

xoxo 💖 from ./fs/lockd, October 2026 — this has been nlmsvc_proc_unlock(9), signing off 🎀