nlm4svc_proc_unlock_msg(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 nlm4svc_proc_unlock_msg(9) — like, the Kernel API Manual page, bestie 🦋

okay so real talk, this is a page from the Kernel API Manual, and it's about nlm4svc_proc_unlock_msg — yes that's a whole mouthful, we love her anyway 💅

✨ NAME ✨

nlm4svc_proc_unlock_msg — UNLOCK_MSG: Remove an existing lock

like... she removes locks. that's the whole vibe. iconic honestly 🎀

🌸 SYNOPSIS 🌸

__be32 nlm4svc_proc_unlock_msg (struct svc_rqst *rqstp );

that's it. one function, one argument, __be32 return. clean, minimal, main character energy ✨

💖 ARGUMENTS 💖

  • rqstp — the RPC transaction context 🫶 like, this is the little bundle of info about the RPC call that's currently happening. she needs it. don't ask questions.

🔥 RETURN 🔥

two possible outcomes, no in-between, periodt:

  • rpc_success — the RPC executed successfully 🎉 slay!!
  • rpc_system_err — the RPC execution failed 💀 not slay, but it happens

🧚 DESCRIPTION 🧚

RPC synopsis, and yes we're quoting it exactly because it's important:

void NLMPROC4_UNLOCK_MSG(nlm4_unlockargs) = 9;

the way that this request works is: the response to it gets delivered via the UNLOCK_RES procedure. so like, you send the message, and the answer comes back through UNLOCK_RES. that's the whole flow, iykyk 🌈

👑 SEE ALSO 👑

lowkey a whole friend group in here, look at the kernel file:

./fs/lockd/svc4proc.c

and her besties (all (9) pages, obviously):

  • nlm4svc_proc_null
  • nlm4svc_proc_test
  • nlm4svc_proc_lock
  • nlm4svc_proc_cancel
  • nlm4svc_proc_unlock
  • nlm4svc_proc_granted
  • nlm4svc_proc_test_msg
  • nlm4svc_proc_lock_msg
  • nlm4svc_proc_cancel_msg
  • nlm4svc_proc_granted_msg
  • nlm4svc_proc_granted_res
  • nlm4svc_proc_sm_notify
  • nlm4svc_proc_unused
  • nlm4svc_proc_share
  • nlm4svc_proc_unshare
  • nlm4svc_proc_nm_lock
  • nlm4svc_proc_free_all

go read them all, they ate 🔥

aaaand that's the page!! sign-off time bestie: this little beauty lives in ./fs/lockd and the version/date stamp on it is October 2026 🗓️💜 okay bye, go unlock some locks (responsibly) 💅💖

📦 where this page comes from