nlmsvc_proc_granted_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ nlmsvc_proc_granted_msg(9) ✨

okay so we're in the Kernel API Manual bestie, and today's main character is nlmsvc_proc_granted_msg(9) πŸŽ€ like yes we're reading kernel lockd internals for fun, that's just who we are now πŸ’…


πŸ’– NAME πŸ’–

nlmsvc_proc_granted_msg β€” GRANTED_MSG: the blocked lock has been granted πŸŽ‰ iykyk, somebody was waiting and now they're not, slay


πŸ¦‹ SYNOPSIS πŸ¦‹

__be32 nlmsvc_proc_granted_msg (struct svc_rqst *rqstp );

🌸 ARGUMENTS 🌸

  • rqstp β€” the RPC transaction context 🫢 literally the whole vibe of this call, it's the request's little passport

⭐ RETURN ⭐

so here's the vibe check on what comes back πŸ‘‘

  • rpc_success β€” RPC executed successfully. ate, no crumbs ✨
  • rpc_garbage_args β€” the request arguments are malformed 😭 like the args showed up in pajamas, we cannot work with this
  • rpc_system_err β€” RPC execution failed πŸ’€ rough one ngl

🌈 DESCRIPTION 🌈

RPC synopsis incoming, copy it exactly bestie:

void NLMPROC_GRANTED_MSG(nlm_testargs) = 10;

and the important bit πŸ‘‡ the response to this request is delivered via the GRANTED_RES procedure. so like, you don't get your answer right here in this call β€” it comes back to you through GRANTED_RES, no cap 🧚


πŸ“ SEE ALSO πŸ“

Kernel file ./fs/lockd/svcproc.c β€” that's the home base 🏠 and the whole friend group of functions, all of them, in order:


okay that's the whole page, go be iconic with your lock grants πŸ¦‹πŸ’œ this little number lives in ./fs/lockd and it's stamped October 2026, so like, future-coded of it honestly βœ¨πŸ‘‘ mwah, study hard bestie πŸ’…

πŸ“¦ where this page comes from