nlm4svc_proc_test(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 NAME 🎀

okay so bestie, this is nlm4svc_proc_test(9) from the Kernel API Manual, and the function is literally named nlm4svc_proc_test — its whole job is TEST: Check for conflicting lock ✨.

🌸 SYNOPSIS 🌸

__be32 nlm4svc_proc_test (struct svc_rqst *rqstp );

🦋 ARGUMENTS 🦋

  • rqstp — RPC transaction context. That's the vibe-check context, periodt.

💖 RETURN 💖

  • rpc_success — RPC executed successfully. slay. 👑
  • rpc_drop_reply — Do not send an RPC reply. like, don't reply, bestie 💅.

🔥 DESCRIPTION 🔥

RPC synopsis, exact and iconic:

nlm4_testres NLMPROC4_TEST(nlm4_testargs) = 1;

Permissible procedure status codes — memorize these, iykyk:

  • NLM4_GRANTED — The server would be able to grant the requested lock. 👑
  • 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_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, no cap:

  • 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, plus this whole bestie squad:

source/version: ./fs/lockd; date: October 2026; page: nlm4svc_proc_test(9). bye bestie, go check those locks 💜🫶

📦 where this page comes from