nlm4svc_proc_sm_notify(9)

💖 NAME 💖

okay so bestie, meet nlm4svc_proc_sm_notify from the Kernel API Manual — its whole personality is SM_NOTIFY: Peer has rebooted. literally the “your peer rebooted, bestie” callback. slay. ✨

🌸 SYNOPSIS 🌸

__be32 nlm4svc_proc_sm_notify (struct svc_rqst *rqstp );

🦋 ARGUMENTS 🦋

• rqstp — RPC transaction context. that’s the one and only argument, periodt. 🫶

🔥 RETURN 🔥

• rpc_success: RPC executed successfully. 💖
• rpc_system_err: RPC execution failed. 😭

👑 DESCRIPTION 👑

The SM_NOTIFY procedure is a private callback from Linux statd, and no cap: it is not part of the official NLM protocol. so if you were looking for it in the official protocol group chat, it’s not there, bestie. 🙈

RPC synopsis: void NLMPROC4_SM_NOTIFY(nlm4_notifyargs) = 16;

🌈 SEE ALSO 🌈

Kernel file ./fs/lockd/svc4proc.c — and the whole reference squad is:

• nlm4svc_proc_null(9)
• nlm4svc_proc_test(9)
• nlm4svc_proc_lock(9)
• nlm4svc_proc_cancel(9)
• nlm4svc_proc_unlock(9)
• nlm4svc_proc_granted(9)
• nlm4svc_proc_test_msg(9)
• nlm4svc_proc_lock_msg(9)
• nlm4svc_proc_cancel_msg(9)
• nlm4svc_proc_unlock_msg(9)
• nlm4svc_proc_granted_msg(9)
• nlm4svc_proc_granted_res(9)
• nlm4svc_proc_unused(9)
• nlm4svc_proc_share(9)
• nlm4svc_proc_unshare(9)
• nlm4svc_proc_nm_lock(9)
• nlm4svc_proc_free_all(9)

mwah 💋 final sign-off: this page lives under source/version ./fs/lockd, dated October 2026, for nlm4svc_proc_sm_notify(9). bye bestie, go read those man pages 🫶🎀