nlmsvc_proc_lock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nlmsvc_proc_lock(9) — a Kernel API Manual moment 🌸

okay so bestie, welcome to the nlmsvc_proc_lock(9) page — yes that's her full government name, and yes she's from the Kernel API Manual, we stan 💖

✨ NAME ✨

nlmsvc_proc_lock — LOCK: Establish a monitored lock 👑

🦋 SYNOPSIS 🦋

__be32 nlmsvc_proc_lock (struct svc_rqst *rqstp );

🎀 ARGUMENTS 🎀

  • rqstp — the RPC transaction context. that's it, that's the whole vibe, she just needs the context bestie 🫶

⭐ RETURN ⭐

  • rpc_success — RPC executed successfully. slay, it worked 💅
  • rpc_drop_reply — Do not send an RPC reply. literally just don't reply, ghost them 🙈

🌈 DESCRIPTION 🌈

RPC synopsis, and I'm gonna give it to you exactly how it is:

nlm_res NLM_LOCK(nlm_lockargs) = 2;

now for the permissible procedure status codes, aka the whole mood board of outcomes — every single one of them, no skipping ✨

  • LCK_GRANTED — The requested lock was granted. iconic behavior, honestly 👑
  • LCK_DENIED — The requested lock conflicted with existing lock reservations for the file. awkward 💀
  • LCK_DENIED_NOLOCKS — The server could not allocate the resources needed to process the request. the server is going through it rn 😭
  • LCK_BLOCKED — The blocking request cannot be granted immediately. The server will send an NLM_GRANTED callback to the client when the lock can be granted. so like… not right now, but she will text you back, promise 🫶
  • 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. she just woke up, give her a minute to do her skincare routine 🧚

🍓 SEE ALSO 🍓

Kernel file ./fs/lockd/svcproc.c — and the whole friend group, fr fr:

ok that's the whole page bestie, go forth and lock responsibly 🦋💜

kisses from ./fs/lockd, dated October 2026, brought to you by the nlmsvc_proc_lock(9) girlies — see u in the group chat 💌🎀

📦 where this page comes from