mesh_path_assign_nexthop(9)

📦 version 7.3.1, in nixpkgs unstable

💫 mesh_path_assign_nexthop(9) 💫

okay so this is a page straight out of the Kernel API Manual — mesh_path_assign_nexthop(9), bestie. yes it's a mouthful, no we're not renaming it, it's iconic as is 🎀

✨ NAME ✨

mesh_path_assign_nexthop — update mesh path next hop

like literally, it's the glow-up function for a mesh path's next hop 💅

🌸 SYNOPSIS 🌸

void mesh_path_assign_nexthop (struct mesh_path *mpath , struct sta_info
*sta );

ngl, void in, vibes out. no return value, she just does the thing 🦋

🧚 ARGUMENTS 🧚

  • mpath — the mesh path you're updating, aka the main character of this whole operation 👑
  • sta — the next hop you're assigning to it, the one getting the crown handed over 🫶

💖 DESCRIPTION 💖

Locking: mpath->state_lock must be held when calling this function.

that's the whole description, and it's not a suggestion — it's giving hard requirement, fr fr. hold that lock or don't call her at all, no cap 😭🔒

⭐ SEE ALSO ⭐

Kernel file ./net/mac80211/mesh_pathtbl.c and honestly her entire friend group:

the whole squad, all together, iykyk 💜

lowkey reminder: this page lives in ./net/mac80211, dated October 2026, and she answers to the name mesh_path_assign_nexthop(9). slay, go hold that lock bestie 💅✨🌈
📦 where this page comes from