mesh_path_error_tx(9)

📦 version 7.3.1, in nixpkgs unstable

💅 mesh_path_error_tx(9) — like, the PERR-sending era 💅

okay so bestie, welcome to the Kernel API Manual ✨ this one lives in the mesh_path_error_tx(9) cinematic universe and it's literally about yeeting a PERR mesh management frame out into the world 🦋

🌸 NAME 🌸

mesh_path_error_tx — sends a PERR mesh management frame, no cap 🎀

✨ SYNOPSIS ✨

int mesh_path_error_tx (struct ieee80211_sub_if_data *sdata , u8 ttl ,
       const u8 *target , u32 target_sn , u16 target_rcode , const u8 *ra );

like, that's the whole vibe. one function, six arguments, zero chill 💅

🫶 ARGUMENTS 🫶

  • sdata — the local mesh subif. that's the main character right there 👑
  • ttl — allowed remaining hops. literally how many hops it's still got left in the tank before it's done 🏃‍♀️
  • target — the broken destination 😭 the one that's not doing so hot
  • target_sn — SN of the broken destination. gotta know the number, iykyk 🔢
  • target_rcode — the reason code for this PERR. like the "why are we here" of the whole frame 🧚
  • ra — node this frame is addressed to, aka who's getting this lil message 💌

💀 NOTE 💀

okay so this is the important bit, don't skip it 🙈

this function may be called with driver locks taken that the driver also acquires in the TX path. and to avoid a deadlock — yes, the scary kind 😭 — we don't transmit the frame directly, we add it to the pending queue instead. that's the whole reason it's like this. periodt. 🔥

bestie this is a real deadlock-avoidance thing, not a vibe. do not go transmitting directly. 💅

⭐ RETURN ⭐

0 on success ✨ that's it, that's the return. slay.

🌈 SEE ALSO 🌈

kernel file ./net/mac80211/mesh_hwmp.c and its whole friend group:

like, go read those too, they're all connected fr fr 🦋

and that's the page bestie!! 🎀 brought to you by the fine folks over at ./net/mac80211, dated October 2026 — mwah, go forth and send your PERRs safely 💖✨

📦 where this page comes from