nlm4svc_proc_lock(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

Okay bestie, welcome to nlm4svc_proc_lock(9) from the Kernel API Manual — this is the page for the function nlm4svc_proc_lock - LOCK: Establish a monitored lock 💅

✨ SYNOPSIS ✨

__be32 nlm4svc_proc_lock (struct svc_rqst *rqstp );

🫶 ARGUMENTS 🫶

  • rqstp — RPC transaction context

💖 RETURN 💖

  • rpc_success: RPC executed successfully.
  • rpc_drop_reply: Do not send an RPC reply.

🔥 DESCRIPTION 🔥

RPC synopsis, bestie: nlm4_res NLMPROC4_LOCK(nlm4_lockargs) = 2;

Permissible procedure status codes — the whole vibe check:

  • NLM4_GRANTED: The requested lock was granted.
  • NLM4_DENIED: The requested lock conflicted with existing lock reservations for the file.
  • NLM4_DENIED_NOLOCKS: The server could not allocate the resources needed to process the request.
  • NLM4_BLOCKED: The blocking request cannot be granted immediately. The server will send an NLMPROC4_GRANTED callback to the client when the lock can be granted.
  • NLM4_DENIED_GRACE_PERIOD: The server has recently restarted and is re-establishing existing locks, and is not yet ready to accept normal service requests.

The Linux NLM server implementation also returns these extra plot twists:

  • NLM4_DEADLCK: The request could not be granted and blocking would cause a deadlock.
  • NLM4_STALE_FH: The request specified an invalid file handle.
  • NLM4_FBIG: The request specified a length or offset that exceeds the range supported by the server.
  • NLM4_FAILED: The request failed for an unspecified reason.

🦋 SEE ALSO 🦋

Kernel file ./fs/lockd/svc4proc.c — go peep these besties too:

Catch you later, bestie! 💜 This iconic little page comes from source/version ./fs/lockd, dated October 2026, and it’s the nlm4svc_proc_lock(9) manual page. 🎀✨

📦 where this page comes from