svcauth_null_accept(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– svcauth_null_accept β€” the Kernel API Manual moment πŸ¦‹

okay so bestie, welcome to the glow-up of svcauth_null_accept(9), straight out of the Kernel API Manual. no cap, this one is a whole vibe check for incoming RPC creds ✨


🌸 NAME 🌸

svcauth_null_accept β€” the function that decodes and validates an incoming RPC_AUTH_NULL credential, and honestly? she's doing both jobs and she's serving πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

enum svc_auth_status svcauth_null_accept (struct svc_rqst *rqstp );

like, that's the whole signature. iconic. not me memorising it fr fr 🫢


✨ ARGUMENTS ✨

  • rqstp β€” the RPC transaction. that's your main character right there, she carries the whole scene πŸ’œ

πŸ’€ DESCRIPTION πŸ’€

so here's the tea, bestie β€” these are the return values, and you gotta know all of them:

  • SVC_OK: both the credential and the verifier are valid. slay, we love a clean pass 🌈
  • SVC_DENIED: the credential or the verifier is not valid. nope, not today πŸ™ˆ
  • SVC_GARBAGE: it failed to decode the credential or the verifier. literally unusable 😭
  • SVC_CLOSE: temporary failure. not a forever thing, just a moment πŸ’€

also, rqstp->rq_auth_stat gets set, as mandated by RFC 5531. that's not optional, that's the rules, periodt πŸ‘‘

like, for real β€” rq_auth_stat is set exactly as RFC 5531 mandates. no improvising, no vibes-based auth, iykyk.

πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, all linked, all valid, all gorgeous 🧚


lowkey a warning bestie: the return values mean completely different things β€” SVC_OK is not the same as SVC_DENIED, and SVC_GARBAGE is not SVC_CLOSE. don't mix them up, that's a bad timeline πŸ’…

and that's the page! mwah πŸ’‹

β€” from ./net/sunrpc, dated October 2026, brought to you by the Kernel API Manual. go off, bestie, you ate this one πŸŒŸπŸ“πŸ’–

πŸ“¦ where this page comes from