nlmsvc_proc_sm_notify(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nlmsvc_proc_sm_notify — like, the "hey bestie I just rebooted" callback

okay so real talk, this is nlmsvc_proc_sm_notify(9) from the Kernel API Manual (section 9, we're in kernel-land now, put some respect on it 🫶). She's a little niche, she's a little private, and honestly? She ate.

✨ SYNOPSIS ✨

__be32 nlmsvc_proc_sm_notify (struct svc_rqst *rqstp );

like, that's the whole vibe. one function, one argument, one __be32 coming back at you 💖

🎀 ARGUMENTS 🎀

  • rqstp — the RPC transaction context. that's it, that's the whole cast of characters. she's the main character energy of this whole page ngl 🌸

🔥 RETURN 🔥

  • rpc_success — RPC executed successfully. slay, it worked 💅
  • rpc_system_err — RPC execution failed. not slay, something went sideways 😭

🦋 DESCRIPTION 🦋

okay so here's the tea ☕: the SM_NOTIFY procedure is a private callback from Linux statd — like a little backchannel DM, not the public group chat — and it is not part of the official NLM protocol. no cap, she's unofficial, she's off-book, she's giving secret-handshake energy 🙈

and the RPC synopsis, verbatim, because we do not paraphrase the sacred texts:

void NLM_SM_NOTIFY(nlm_notifyargs) = 16;

basically: peer has rebooted. that's the whole message. "hey bestie, I restarted, please handle my locks accordingly" — iconic, minimal, efficient 💯

🌈 SEE ALSO 🌈

the kernel file ./fs/lockd/svcproc.c, plus the entire friend group (yes, all of them, I'm not skipping a single one, we don't do that here):

fr fr, read them all. they're a package deal, iykyk 💜

and that's the page!! 🎀 signed, sealed, delivered from ./fs/lockd, dated October 2026, in the nlmsvc_proc_sm_notify(9) era. go forth and reboot responsibly bestie 🦋✨

📦 where this page comes from