nlm4_svc_de...lm4_lockargs(9)

✨ NAME ✨

okay so bestie, this is the nlm4_svc_decode_nlm4_lockargs page from the Kernel API Manual (yes, the Kernel API Manual, we're in the big leagues now 💅) — and it does exactly one thing: it decodes a nlm4_lockargs argument. that's it. that's the whole gig. 🎀

---

🦋 SYNOPSIS 🦋

bool nlm4_svc_decode_nlm4_lockargs (struct svc_rqst *rqstp , struct
       xdr_stream *xdr );

like, look at her go ✨ returns a bool, takes two pointers, no cap.

---

💖 ARGUMENTS 💖

• rqstp — the RPC transaction context, aka the whole vibe of the request you're currently living in 🫶
• xdr — the source XDR data stream, i.e. where the raw bytes are actually coming from 🍓

---

🌸 DESCRIPTION 🌸

so the return values are literally the entire plot:

• true — procedure arguments decoded successfully. slay. it ate. 🔥
• false — decode failed. 😭 not the vibe, but at least you know.

that's the whole description, bestie — no hidden lore, no secret options, this function is refreshingly low-drama 💀

---

👑 SEE ALSO 👑

kernel file ./fs/lockd/nlm4xdr_gen.c — go read the source, iykyk 📖

and the whole friend group of sibling functions, all iconics in their own right:

• nlm4_svc_decode_nlm4_testargs(9)
• nlm4_svc_decode_nlm4_cancargs(9)
• nlm4_svc_decode_nlm4_unlockargs(9)
• nlm4_svc_decode_nlm4_testres(9)
• nlm4_svc_decode_nlm4_res(9)
• nlm4_svc_decode_nlm4_notifyargs(9)
• nlm4_svc_decode_nlm4_shareargs(9)
• nlm4_svc_decode_nlm4_notify(9)
• nlm4_svc_encode_nlm4_testres(9)
• nlm4_svc_encode_nlm4_res(9)
• nlm4_svc_encode_nlm4_shareres(9)

---

and that's a wrap, bestie!! 🧚 this lil slice of kernel lore comes to you from ./fs/lockd, dated October 2026 — so go forth, decode those lockargs, and remember: main character energy only 💜✨