nlmsvc_proc_unlock_msg(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nlmsvc_proc_unlock_msg(9) — Kernel API Manual 🎀

okay so bestie, welcome to the lockd girlies' chapter of the Kernel API Manual — today's main character is nlmsvc_proc_unlock_msg, and honestly? she's the one who cleans up after everybody else. iconic behaviour fr fr.

✨ NAME ✨

nlmsvc_proc_unlock_msg — UNLOCK_MSG: Remove an existing lock 🗝️

like, she takes the lock off. that's the whole vibe. no notes.

🌸 SYNOPSIS 🌸

__be32 nlmsvc_proc_unlock_msg (struct svc_rqst *rqstp );

🦋 ARGUMENTS 🦋

  • rqstp — the RPC transaction context, aka the little backpack of info about the call that's currently happening. she carries it everywhere. 🎒

💜 RETURN 💜

so here's what she can hand back to you, and like — each one is a whole mood:

  • rpc_success — RPC executed successfully. slay, we ate. ✨
  • rpc_drop_reply — Do not send an RPC reply. literally ghosting, on purpose, by design. 💀
  • rpc_garbage_args — The request arguments are malformed. the vibes were off, the args were giving nonsense, we can't work with this. 🙈
  • rpc_system_err — RPC execution failed. it's not her fault, the system said no. 😭

🔥 DESCRIPTION 🔥

RPC synopsis, in her full little outfit:

void NLMPROC_UNLOCK_MSG(nlm_unlockargs) = 9;

and here's the tea: the response to this request doesn't come back the normal way — it's delivered via the UNLOCK_RES procedure. so like, don't wait around at this door, bestie, the reply is being delivered somewhere else entirely. 🧚

👑 SEE ALSO 👑

Kernel file ./fs/lockd/svcproc.c — that's where the whole squad lives:

ok so that's the whole page. every flag, every return value, every sibling function — all accounted for, no cap. 💅

and finally, the cute little sign-off: this one lives in ./fs/lockd, dated October 2026, and it's filed under nlmsvc_proc_unlock_msg(9). 🫶 bye bestie, go unlock something responsibly ✨🌈

📦 where this page comes from