batadv_wifi...evice_update(9)
π
batadv_wifi_net_device_update β Kernel API Manual
okay so bestie, welcome to the manual page for batadv_wifi_net_device_update(9) π¦ this one lives in the Kernel API Manual and honestly? it's giving "small function, big responsibilities" energy. let's get into it β¨
πΈ NAME πΈ
batadv_wifi_net_device_update β update wifi state of net_device
likeβ¦ it updates the wifi state. of a net_device. that's the whole vibe π
β¨ SYNOPSIS β¨
void batadv_wifi_net_device_update (struct net_device *net_dev );
one function, one argument, void return because it doesn't need to hand you anything back β it just does the thing and leaves π
π«Ά ARGUMENTS π«Ά
net_devβ the net_device to update inbatadv_wifi_net_devices. that's it, that's the whole argument list, just your one little network device showing up to get its status refreshed π
π₯ DESCRIPTION π₯
okay so here's the tea β the device only gets stored in batadv_wifi_net_devices when it could be identified as a wifi device. that's the entry requirement, no exceptions, the bouncer is checking IDs at the door π
and if the net_device is no longer a wifi device? it gets automatically removed from batadv_wifi_net_devices. not me ghosting the list the second the wifi vibe is gone π it's self-cleaning, it's efficient, it's lowkey iconic.
so basically: wifi device β you're in the list π«Ά not a wifi device anymore β bye bestie, you're out π and batadv_wifi_net_device_update is the one making that call.
π SEE ALSO π
all the siblings and cousins in the family, fr fr β this function does not exist in a vacuum:
kernel file ./net/batman-adv/hard-interface.c, plus:
batadv_hardif_release(9)batadv_hardif_get_by_netdev(9)batadv_getlink_net(9)batadv_mutual_parents(9)batadv_is_on_batman_iface(9)batadv_is_valid_iface(9)__batadv_get_real_netdev(9)batadv_get_real_netdev(9)batadv_is_wext_netdev(9)batadv_is_cfg80211_netdev(9)batadv_wifi_flags_evaluate(9)batadv_netdev_get_wifi_flags(9)batadv_hardif_get_wifi_flags(9)batadv_is_wifi_hardif(9)batadv_hardif_no_broadcast(9)batadv_hardif_get_active(9)batadv_primary_if_update_addr(9)batadv_primary_if_select(9)batadv_hardif_is_iface_up(9)batadv_check_known_mac_addr(9)batadv_hardif_recalc_extra_skbroom(9)batadv_hardif_min_mtu(9)batadv_update_min_mtu(9)batadv_hardif_activate_interface(9)batadv_hardif_deactivate_interface(9)batadv_hardif_enable_interface(9)batadv_hardif_disable_interface(9)batadv_hard_if_event_meshif(9)batadv_wifi_net_device_insert(9)batadv_wifi_net_device_remove(9)batadv_wifi_net_device_unregister(9)batadv_wifi_net_device_event(9)batadv_hard_if_event(9)batadv_wifi_net_devices_init(9)batadv_wifi_net_devices_deinit(9)
like, that's a whole friend group π§ and yes you should probably read at least a couple of them. iykyk π
vibe check: this page is short and sweet β no options, no flags, no exit statuses to memorise. just one device, one list, and one very clear rule about who gets to stay π
that's the whole page bestie, slay π this one's brought to you from ./net/batman-adv, dated October 2026, and titled batadv_wifi_net_device_update(9) β go forth and update those wifi states, no cap π β¨
π¦ 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