svc_thread_init_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… svc_thread_init_status(9) β€” the "did my thread survive init" check-in

okay so bestie, welcome to the kernel API manual, section 9 of the manual pages, and today's main character is svc_thread_init_status ✨ she's a void function, she's lowkey dramatic (she might never return 😭), and she's here to tell the world whether a thread actually got its life together. let's get into it 🫢


🌸 NAME 🌸

svc_thread_init_status β€” the function that reports whether a thread has initialised successfully. that's it, that's the whole vibe check πŸ’–


✨ SYNOPSIS ✨

void svc_thread_init_status (struct svc_rqst *rqstp , int err );

two args, no return value, no cap. she just does her thing πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • rqstp β€” the thread in question. like, this thread. the one we're talking about πŸ‘€
  • err β€” an errno code. a number that says how it went, basically πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the situation. after a sunrpc svc_thread does any of its initialisation that could potentially fail, and before it starts doing its normal work, it must call svc_thread_init_status β€” and it has to pass in an appropriate error, or zero if everything's chill πŸ“

so like:

  • if you pass zero, the thread is ready, she's thriving, and she must continue until svc_thread_should_stop returns true πŸ‘‘
  • if you pass a non-zero error, uh. the call will not return. πŸ’€ like literally never comes back β€” the thread will exit. not me writing a function that ghosts you mid-call 😭
heads up bestie: that non-zero case is not a soft failure, the call genuinely doesn't return. the thread's gone. periodt πŸ™ˆ

🌈 SEE ALSO 🌈

kernel file ./include/linux/sunrpc/svc.h, and also these absolute icons:


and that's the page, bestie 🧚 she lives in ./include/linux/sunrpc, and this particular glow-up was dated October 2026 β€” mwah, go forth and init responsibly πŸ’œπŸŽ€

πŸ“¦ where this page comes from