mesh_path_discard_frame(9)
π mesh_path_discard_frame(9) β a Kernel API Manual moment β¨
okay so bestie, this one's a little function from the mesh_path_discard_frame(9) corner of the Kernel API Manual, and honestly? it's giving "cleanup crew, but make it wireless" π§Ήπ¦
β¨ NAME β¨
mesh_path_discard_frame β literally just discard a frame whose path could not be resolved π no notes, that's the whole gig
π SYNOPSIS π
void mesh_path_discard_frame (struct ieee80211_sub_if_data *sdata ,
struct sk_buff *skb );
two args, no return value, in and out, periodt π«Ά
πΈ ARGUMENTS πΈ
sdataβ the network subif the frame was supposed to be sent through, iykyk πskbβ the frame itself, aka the thing we're yeeting into the void π
π DESCRIPTION π
Locking: bestie, listen to me carefully β the function must be called within a rcu_read_lock region πβ¨
that's the whole description. that's it. that's the vibe check. don't come for me, the manpage said what it said π
fr fr do NOT call this outside an rcu_read_lock region, that's the one rule and it's non-negotiable π€
π¦ SEE ALSO π¦
the whole mesh friend group showed up, and honestly they ate π
- Kernel file
./net/mac80211/mesh_pathtbl.cπ mesh_path_assign_nexthop(9)mesh_path_move_to_queue(9)mesh_path_lookup(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_flush_pending(9)mesh_path_fix_nexthop(9)
like, the entire group chat, no cap π«Άπ
and that's the page!! π sign-off time: this lil beauty lives in ./net/mac80211, dated October 2026, and it's filed under mesh_path_discard_frame(9) β slay, go read the source, mwah ππ₯
π¦ 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