nlm4svc_proc_lock_msg(9)

💅 nlm4svc_proc_lock_msg(9) 💅

okay so bestie, welcome to the Kernel API Manual corner where we make kernel RPC entry points make sense. This one is nlm4svc_proc_lock_msg, aka the LOCK_MSG glow-up: Establish a monitored lock. ✨

---

🎀 NAME 🎀

nlm4svc_proc_lock_msg — LOCK_MSG: Establish a monitored lock.

🌸 SYNOPSIS 🌸

__be32 nlm4svc_proc_lock_msg (struct svc_rqst *rqstp );

that’s the whole signature, no cap: __be32 return type, one argument, we move. 🫶

🦋 ARGUMENTS 🦋

• rqstp — the RPC transaction context. literally the context for this RPC transaction; keep it close. 💖

⭐ RETURN ⭐

• rpc_success — RPC executed successfully. slay. ✨
• rpc_system_err — RPC execution failed. 💀

🔥 DESCRIPTION 🔥

RPC synopsis check, bestie:

void NLMPROC4_LOCK_MSG(nlm4_lockargs) = 7;

The response to this request is delivered via the LOCK_RES procedure. that’s the tea: response delivery goes through LOCK_RES. 👑

🌈 SEE ALSO 🌈

Kernel file: ./fs/lockd/svc4proc.c — yes, that’s the spot. 👀

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_cancel_msg(9)
• nlm4svc_proc_unlock_msg(9)
• nlm4svc_proc_granted_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)

---

later, babe — this page lives at ./fs/lockd, dated October 2026, and it’s nlm4svc_proc_lock_msg(9) from the Kernel API Manual. 🫶💖