mesh_path_lookup(9)
π
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'sETH_ALENlength, 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:
mesh_path_assign_nexthop(9)mesh_path_move_to_queue(9)mesh_path_lookup_by_idx(9)mpp_path_lookup_by_idx(9)mesh_path_add_gate(9)mesh_gate_del(9)mesh_gate_num(9)mesh_path_add(9)mesh_plink_broken(9)mesh_path_flush_by_nexthop(9)mesh_path_flush_by_iface(9)table_path_del(9)mesh_path_del(9)mesh_path_tx_pending(9)mesh_path_send_to_gates(9)mesh_path_discard_frame(9)mesh_path_flush_pending(9)mesh_path_fix_nexthop(9)
π 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms