nsm_get_handle(9)

📦 version 7.3.1, in nixpkgs unstable

💖 nsm_get_handle(9) — Kernel API Manual 💖

🌸 NAME 🌸

nsm_get_handle — Find or create a cached nsm_handle. It’s giving “handle matchmaking” energy, bestie: either it finds the cached one or it makes a fresh one. 💅

✨ SYNOPSIS ✨

Okay so here’s the exact signature, character for character — do not touch, no cap:

struct nsm_handle * nsm_get_handle (const struct net *net , const struct sockaddr *sap , const size_t salen , const char *hostname , const size_t hostname_len );

🫶 ARGUMENTS 🫶

  • net — network namespace. That’s the whole vibe’s scope, iykyk. 🌐
  • sap — pointer to socket address of handle to find. The address bestie we’re matching against. 📍
  • salen — length of socket address. Gotta know how much address we’re working with. 📏
  • hostname — pointer to C string containing hostname to find. The name-search side of the mission. 🏷️
  • hostname_len — length of C string. Yes, the length of that hostname string. 💖

🦋 DESCRIPTION 🦋

Real talk: behavior is modulated by the global nsm_use_hostnames variable. That’s the switchboard for this whole situation. 🎛️

It returns a cached nsm_handle after bumping its ref count, or returns a fresh nsm_handle if a handle that matches sap and/or hostname cannot be found in the handle cache. Basically: cache hit, slay; cache miss, fresh handle moment. 🔥

Returns NULL if an error occurs. So if you get NULL, that’s the error signal — not a vibe, bestie. 😭

🌈 SEE ALSO 🌈

Kernel file ./fs/lockd/mon.c plus these iconic little references:

mwah 💋 source/version: ./fs/lockd; date: October 2026 — that’s the cute sign-off, periodt. 🎀

📦 where this page comes from