mesh_path_lookup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mesh_path_lookup (9) β€” from the Kernel API Manual πŸŽ€

Ok so bestie, gather round, because today we're looking up a path in the mesh path table and honestly? It's giving essential infrastructure. ✨


🌸 NAME 🌸

mesh_path_lookup β€” look up a path in the mesh path table, no cap πŸ”


✨ SYNOPSIS ✨

struct mesh_path * mesh_path_lookup (struct ieee80211_sub_if_data *sdata
, const u8 *dst );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • sdata β€” the local subif, like, the sub-iface you're working with πŸ’–
  • dst β€” the hardware address of the destination, and yes it's ETH_ALEN length, so don't @ me with a shorter one πŸ™ˆ

πŸ‘‘ RETURN πŸ‘‘

It hands you back a pointer to the mesh path structure 🫢 β€” or NULL if it wasn't found. That's it. That's the vibe check.


πŸ’œ DESCRIPTION πŸ’œ

Locking: you must call this within a read RCU section. Not optional, not a suggestion, not a "maybe later" β€” fr fr, respect the RCU section or perish 😭πŸ”₯


🌈 SEE ALSO 🌈

The kernel file ./net/mac80211/mesh_pathtbl.c is where all the magic lives, and here's the whole squad it runs with:


πŸ’€ Reminder bestie: read RCU section or it doesn't count. That's the whole locking contract and she is not flexible about it.

Okkk that's the page! 🧚 Signing off from ./net/mac80211 in October 2026, brought to you by the mesh_path_lookup(9) girlies β€” slay, stay safe, and may all your lookups return non-NULL πŸ’…πŸ’–πŸ“

πŸ“¦ where this page comes from