nlmsvc_proc_lock_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME β€” nlmsvc_proc_lock_msg(9) πŸ’–

okay so bestie, welcome to nlmsvc_proc_lock_msg(9) from the Kernel API Manual πŸ’… this one is LOCK_MSG: establishing a monitored lock. that’s the whole name vibe, periodt.


🌸 SYNOPSIS 🌸

here’s the signature, and yes we keep it exactly:

__be32 nlmsvc_proc_lock_msg (struct svc_rqst *rqstp );

πŸŽ€ ARGUMENTS πŸŽ€

  • rqstp β€” the RPC transaction context. that’s the argument, bestie 🫢

πŸ’… RETURN πŸ’…

the return values are giving β€œpick one,” so here’s every single one:

  • rpc_success β€” RPC executed successfully. slay ✨
  • rpc_drop_reply β€” Do not send an RPC reply. literally no reply πŸ«₯
  • rpc_garbage_args β€” The request arguments are malformed. πŸ—‘οΈ
  • rpc_system_err β€” RPC execution failed. 😭

πŸ¦‹ DESCRIPTION πŸ¦‹

RPC synopsis: void NLMPROC_LOCK_MSG(nlm_lockargs) = 7;

the response to this request is delivered via the LOCK_RES procedure. iykyk πŸ’«


🌈 SEE ALSO 🌈

Kernel file ./fs/lockd/svcproc.c β€” and here are all the sibling pages, no skips:

k bye bestie πŸ’– source/version: ./fs/lockd Β· date: October 2026 β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from