cfg80211_assoc_failure(9)
πΈ NAME πΈ
Okay so this is cfg80211_assoc_failure β it's from the Kernel API Manual (that's the manual this page lives in, bestie, folding it in up top like a good host) β and the whole vibe of this function is: notification of association failure. That's it. That's the job. It tells the world that an association attempt didn't work out π
β¨ SYNOPSIS β¨
Here's the signature, and I'm giving it to you exactly as it is, no edits, no vibes-based rewriting of the code:
void cfg80211_assoc_failure (struct net_device *dev , struct
cfg80211_assoc_failure *data );
Notice the line break in there? Yeah. That's how it is. We respect it. π«Ά
π ARGUMENTS π
Two arguments, both certified load-bearing:
devβ the network device. Like, the actual net device we're talking about here πdataβ the data describing the association failure. Yes, the struct is literally named after the function, that's just how it goes. It's the receipts for why the association flopped π§Ύ
π¦ DESCRIPTION π¦
Okay so this is the part where you need to lock in, because there are two facts here and both of them will get you if you skip them:
This function may sleep. Not "might", not "under some conditions" β it may sleep. Plan accordingly. π΄π
And the second one:
The caller must hold the correspondingwdev's mutex. Not a mutex. Not some mutex nearby. The correspondingwdev's mutex. So if you're about to call this and you're not holding it, put your hands down, you are not ready π
Lowkey that's the whole page β the function announces that an association failed, it can sleep, and you gotta be holding that wdev mutex when you call it. Simple. Iconic. Very "small function, big consequences" energy π
and yes bestie, there's more where that came from β hang tight π
π SEE ALSO π
okay bestie, buckle up, because this is the part where the manpage stops being a manpage and starts being a whole extended universe. it's giving "linked list of destiny", it's giving "the kernel said 'here, have β¨everythingβ¨'". every single cross-reference is down below, nothing skipped, nothing merged, because the kernel does not do abridged versions. π
Kernel file ./include/net/cfg80211.hβ the mothership, the source of truth, the main character's actual houseIntroduction(9),Device registration(9)β start here if you're brand new, no gatekeeping π«Ά
π¦ the "what even is a radio" cluster
your whole physical-layer lore drop, all in one place:
enum ieee80211_channel_flags(9),struct ieee80211_channel(9)β channels, flags, the whole vibe checkenum ieee80211_rate_flags(9),struct ieee80211_rate(9)β rates, and the flags that come with themenum ieee80211_bss_type(9),enum ieee80211_privacy(9)β what kind of BSS it is, and whether it's locked downstruct ieee80211_he_obss_pd(9),struct cfg80211_he_bss_color(9)β HE obss pd and bss color, iconic duo honestlystruct ieee80211_sta_ht_cap(9),struct ieee80211_sta_vht_cap(9)β HT and VHT caps, the classicsstruct ieee80211_sta_he_cap(9),struct ieee80211_eht_mcs_nss_supp(9),struct ieee80211_sta_eht_cap(9)β HE and EHT, we're going deeper πΈstruct ieee80211_sta_uhr_cap(9)β UHR cap, yes she went there
π bands, EDMG, S1G & the iftype data girlies
this is the part where it gets specific. obsessed.
struct ieee80211_sband_iftype_data(9),enum ieee80211_edmg_bw_config(9),struct ieee80211_edmg(9),struct ieee80211_sta_s1g_cap(9)β EDMG bandwidth config, EDMG itself, and the S1G capstruct ieee80211_supported_band(9)β the band that your driver actually supports, periodt_ieee80211_set_sband_iftype_data(9),ieee80211_set_sband_iftype_data(9)β setting that iftype data (note the underscore one, she's the internal sister, don't mix them up π)for_each_sband_iftype_data(9)β the blessed iterator, iykykieee80211_get_sband_iftype_data(9),ieee80211_get_he_iftype_cap(9),ieee80211_get_he_6ghz_capa(9),ieee80211_get_eht_iftype_cap(9),ieee80211_get_uhr_iftype_cap(9)β the getter squad, each one literally named for exactly what it getswiphy_read_of_freq_limits(9)β reading freq limits from device tree, lowkey essential
β¨ ACTIONS AND CONFIGURATION β the big one
bestie this section is huge, I'm not gonna lie to you. but I promised no skipping, so here we go, one bullet at a time. π
Actions and configuration(9)β the section itself, the group chat adminstruct vif_params(9),struct key_params(9)β vif params and key params, straightforward slaystruct cfg80211_chan_def(9)β the channel definition, the blueprintstruct cfg80211_tid_cfg(9),struct cfg80211_tid_config(9)β tid cfg and tid config, yes they're two different things, don't @ mestruct cfg80211_fils_aad(9),struct cfg80211_set_hw_timestamp(9)β FILS AAD and hw timestamp settingcfg80211_get_chandef_type(9),cfg80211_chandef_create(9),cfg80211_chandef_identical(9)β get the type, create one, check if two are identicalcfg80211_chandef_is_edmg(9),cfg80211_chandef_is_s1g(9)β the "is it though?" twinscfg80211_chandef_compatible(9),nl80211_chan_width_to_mhz(9),cfg80211_chandef_get_width(9)β compatibility, width in MHz, and getting the widthcfg80211_chandef_valid(9),cfg80211_chandef_usable(9)β valid vs usable, both matter, don't confuse them πcfg80211_chandef_dfs_required(9),cfg80211_chandef_dfs_usable(9),cfg80211_chandef_dfs_cac_time(9)β the entire DFS trio: required, usable, and the CAC timecfg80211_chandef_primary(9),cfg80211_chandef_npca_valid(9),cfg80211_chandef_add_npca(9),cfg80211_chandef_add_dbe(9)β primary channel, NPCA validity, adding NPCA, adding DBEnl80211_send_chandef(9),ieee80211_chandef_max_power(9),cfg80211_chandef_s1g_pri_width(9)β send it, max power, S1G primary widthcfg80211_any_usable_channels(9)β "is any channel usable?" the eternal questionenum survey_info_flags(9),struct survey_info(9)β survey flags and survey infostruct cfg80211_crypto_settings(9)β crypto settings, the whole security vibestruct cfg80211_mbssid_config(9),struct cfg80211_mbssid_elems(9),struct cfg80211_rnr_elems(9)β MBSSID config, MBSSID elems, and RNR elemsstruct cfg80211_beacon_data(9),struct cfg80211_acl_data(9)β beacon data and ACL datastruct cfg80211_fils_discovery(9),struct cfg80211_unsol_bcast_probe_resp(9)β FILS discovery and the unsolicited broadcast probe response (yes that's the whole name, she's long but she's valid)struct cfg80211_s1g_short_beacon(9)β the S1G short beacon πstruct cfg80211_ap_settings(9),struct cfg80211_ap_update(9)β AP settings and AP update, setting up vs updatingstruct cfg80211_csa_settings(9),struct cfg80211_color_change_settings(9)β channel switch announcement settings, and color change settingsstruct iface_combination_params(9)β interface combination params, the "how many at once" mathenum station_parameters_apply_mask(9),struct sta_txpwr(9)β the apply mask enum and sta txpwrstruct link_station_parameters(9),struct link_station_del_parameters(9),struct cfg80211_ttlm_params(9)β link station add params, link station del params, and TTLM paramsstruct station_parameters(9),struct station_del_parameters(9),enum cfg80211_station_type(9)β station params, station del params, station type enumcfg80211_check_station_change(9)β literally checks a station change, she does what her name says πenum rate_info_flags(9),enum rate_info_bw(9),struct rate_info(9)β rate info flags, rate info bandwidth, rate info struct β a whole trioenum bss_param_flags(9),struct sta_bss_parameters(9)β BSS param flags and sta BSS parametersstruct cfg80211_txq_stats(9),struct cfg80211_tid_stats(9)β txq stats and tid statsstruct link_station_info(9),struct station_info(9)β link station info and the classic station infostruct cfg80211_sar_sub_specs(9),struct cfg80211_sar_specs(9),struct cfg80211_sar_freq_ranges(9),struct cfg80211_sar_capa(9)β the entire SAR family: sub specs, specs, freq ranges, and capa πcfg80211_get_station(9)β get the station, 10/10 descriptiveenum monitor_flags(9),enum mpath_info_flags(9),struct mpath_info(9)β monitor flags, mpath info flags, mpath infoenum wiphy_bss_param_flags(9),struct bss_parameters(9)β wiphy BSS param flags and BSS parametersstruct mesh_config(9),struct mesh_setup(9)β mesh config and mesh setup, the mesh girliesstruct ocb_setup(9)β OCB setup, riding that wave π¦struct ieee80211_txq_params(9)β txq params, last but never least
πΈ SCANNING AND BSS LIST HANDLING
the "who's out there" chapter, and honestly it ate:
Scanning and BSS list handling(9)β the section header herselfstruct cfg80211_ssid(9),struct cfg80211_scan_info(9)β SSID and scan infostruct cfg80211_scan_6ghz_params(9),struct cfg80211_scan_request(9)β the 6GHz scan params and the scan requeststruct cfg80211_match_set(9),struct cfg80211_sched_scan_plan(9)β match set and scheduled scan planstruct cfg80211_bss_select_adjust(9),struct cfg80211_sched_scan_request(9)β BSS select adjust and sched scan requestenum cfg80211_signal_type(9),struct cfg80211_inform_bss(9)β signal type enum and inform BSSstruct cfg80211_bss_ies(9),struct cfg80211_bss(9)β BSS IEs and the BSS itself, icons onlyieee80211_bss_get_elem(9),ieee80211_bss_get_ie(9)β get elem, get ie, two flavors, both validstruct cfg80211_auth_request(9)β auth request, where the handshake beginsstruct cfg80211_assoc_link(9),struct cfg80211_ml_reconf_req(9),enum cfg80211_assoc_req_flags(9),struct cfg80211_assoc_request(9)β assoc link, ML reconf req, assoc req flags, assoc request β the whole assoc friend group π«Άstruct cfg80211_deauth_request(9),struct cfg80211_disassoc_request(9)β deauth and disassoc requests, the sad endingsstruct cfg80211_ibss_params(9),struct cfg80211_bss_selection(9),struct cfg80211_connect_params(9)β IBSS params, BSS selection, connect paramsenum cfg80211_connect_params_changed(9),enum wiphy_params_flags(9)β connect params changed, and wiphy params flagsstruct cfg80211_pmksa(9),struct cfg80211_pkt_pattern(9)β PMKSA and packet patternstruct cfg80211_wowlan_tcp(9),struct cfg80211_wowlan(9)β wowlan TCP and wowlanstruct cfg80211_coalesce_rules(9),struct cfg80211_coalesce(9)β coalesce rules and coalescestruct cfg80211_wowlan_nd_match(9),struct cfg80211_wowlan_nd_info(9),struct cfg80211_wowlan_wakeup(9)β wowlan nd match, nd info, and wakeupstruct cfg80211_gtk_rekey_data(9),struct cfg80211_update_ft_ies_params(9)β GTK rekey data and update FT IEs paramsstruct cfg80211_mgmt_tx_params(9)β management tx paramsstruct cfg80211_dscp_exception(9),struct cfg80211_dscp_range(9),struct cfg80211_qos_map(9)β DSCP exception, DSCP range, and the QoS map
π NAN, PMK, PMSR, and the wiphy extended universe
this is the deepest lore in the whole page and I need you to stay with me, bestie π
Neighbor Awareness Networking (NAN)(9)β NAN, the sectionstruct cfg80211_nan_band_config(9),struct cfg80211_nan_conf(9),struct cfg80211_nan_channel(9)β NAN band config, nan conf, nan channelstruct cfg80211_nan_local_sched(9),struct cfg80211_nan_peer_map(9),struct cfg80211_nan_peer_sched(9)β local sched, peer map, peer schedenum cfg80211_nan_conf_changes(9),struct cfg80211_nan_func_filter(9),struct cfg80211_nan_func(9)β nan conf changes, func filter, and the nan funcstruct cfg80211_pmk_conf(9),struct cfg80211_external_auth_params(9)β PMK conf and external auth paramsstruct cfg80211_ftm_responder_stats(9)β FTM responder statsstruct cfg80211_pmsr_ftm_result(9),struct cfg80211_pmsr_result(9)β PMSR FTM result and PMSR resultstruct cfg80211_pmsr_ftm_request_peer(9),struct cfg80211_pmsr_request_peer(9),struct cfg80211_pmsr_request(9)β FTM request peer, request peer, and the request itselfstruct cfg80211_update_owe_info(9),struct mgmt_frame_regs(9)β update OWE info and mgmt frame regsstruct cfg80211_ops(9)β the ops struct, the driver's whole personalityenum wiphy_flags(9)β wiphy flags enumstruct ieee80211_iface_limit(9),struct ieee80211_iface_combination(9)β iface limit and iface combinationenum wiphy_wowlan_support_flags(9),struct wiphy_wowlan_support(9),struct wiphy_coalesce_support(9)β wowlan support flags, wowlan support, coalesce supportenum wiphy_vendor_command_flags(9),enum wiphy_opmode_flag(9),struct sta_opmode_info(9),struct wiphy_vendor_command(9)β vendor command flags, opmode flag, sta opmode info, vendor commandstruct wiphy_iftype_ext_capab(9),cfg80211_get_iftype_ext_capa(9)β iftype ext capab and the getter for itstruct cfg80211_pmsr_capabilities(9),struct wiphy_iftype_akm_suites(9)β PMSR capabilities and iftype AKM suitesstruct wiphy_radio_cfg(9),struct wiphy_radio_freq_range(9),struct wiphy_radio(9)β radio cfg, radio freq range, radioenum wiphy_nan_flags(9),struct wiphy_nan_capa(9)β wiphy NAN flags and NAN capastruct wiphy(9)β the big wiphy, undisputed main character energy πwiphy_priv(9),priv_to_wiphy(9)β priv, and back to wiphy againset_wiphy_dev(9),wiphy_dev(9),wiphy_name(9)β set the dev, get the dev, get the namewiphy_new_nm(9),wiphy_new(9)β new with a name, and plain newwiphy_register(9),rcu_dereference_wiphy(9),wiphy_dereference(9),get_wiphy_regdom(9)β register, RCU deref, deref, and get regdomwiphy_unregister(9),wiphy_free(9)β unregister, then free, in that order, please πwiphy_lock(9),wiphy_unlock(9)β lock and unlock, the sacred pairwiphy_work_queue(9),wiphy_work_cancel(9),wiphy_work_flush(9)β queue it, cancel it, flush itwiphy_delayed_work_queue(9),wiphy_delayed_work_cancel(9),wiphy_delayed_work_flush(9),wiphy_delayed_work_pending(9)β the delayed flavor: queue, cancel, flush, pendingwiphy_hrtimer_work_queue(9),wiphy_hrtimer_work_cancel(9),wiphy_hrtimer_work_flush(9),wiphy_hrtimer_work_pending(9)β and the hrtimer flavor: queue, cancel, flush, pendingenum ieee80211_ap_reg_power(9)β AP regulatory power enumstruct wireless_dev(9),wdev_priv(9),wdev_chandef(9)β wireless dev, wdev priv, wdev chandef β¨
π§ UTILITY FUNCTIONS
the little helpers that fix everything, honestly the backstage crew:
Utility functions(9)β section headerieee80211_channel_equal(9)β are two channels equal? asks and answersieee80211_channel_to_khz(9),ieee80211_channel_to_freq_khz(9),ieee80211_channel_to_frequency(9)β three ways to go from channel to a numberieee80211_freq_khz_to_channel(9),ieee80211_frequency_to_channel(9)β and two ways to go backieee80211_get_channel_khz(9),ieee80211_get_channel(9)β get channel, khz flavor and classiccfg80211_channel_is_psc(9)β is it a PSC? π¦ieee80211_radio_freq_range_valid(9),cfg80211_radio_chandef_valid(9),cfg80211_wdev_channel_allowed(9)β valid freq range, valid chandef, allowed channelieee80211_get_response_rate(9),ieee80211_mandatory_rates(9)β get the response rate, get the mandatory ratesstruct ieee80211_radiotap_iterator(9)β the radiotap iteratorieee80211_get_hdrlen_from_skb(9),ieee80211_hdrlen(9),ieee80211_get_mesh_hdrlen(9)β header length three ways: from skb, plain, and mesh
π DATA PATH HELPERS
the "get the packet where it's going" club:
Data path helpers(9)β section headerieee80211_data_to_8023_exthdr(9),ieee80211_data_to_8023(9)β data to 8023, with the exthdr variantieee80211_is_valid_amsdu(9),ieee80211_amsdu_to_8023s(9)β is it valid AMSDU, and AMSDU to 8023sieee80211_get_8023_tunnel_proto(9),ieee80211_strip_8023_mesh_hdr(9)β get the 8023 tunnel proto, strip the 8023 mesh headercfg80211_classify8021d(9)β classify 802.1d, she sorts it outcfg80211_find_elem_match(9),cfg80211_find_ie_match(9)β find elem match and find ie matchcfg80211_find_elem(9),cfg80211_find_ie(9)β find elem and find iecfg80211_find_ext_elem(9),cfg80211_find_ext_ie(9)β the extended twinscfg80211_find_vendor_elem(9),cfg80211_find_vendor_ie(9)β vendor elem and vendor ieenum cfg80211_rnr_iter_ret(9),cfg80211_iter_rnr(9)β RNR iter return enum and the iter itselfcfg80211_defragment_element(9)β defragment that elementcfg80211_send_layer2_update(9)β send the layer 2 update
π REGULATORY ENFORCEMENT INFRASTRUCTURE
the "what am I even allowed to transmit" chapter, very responsible of you:
Regulatory enforcement infrastructure(9)β section headerregulatory_hint(9)β drop a hint to the regulatory systemregulatory_set_wiphy_regd(9),regulatory_set_wiphy_regd_sync(9)β set the wiphy regd, plus the sync versionwiphy_apply_custom_regulatory(9)β apply custom regulatoryfreq_reg_info(9)β frequency regulatory inforeg_initiator_name(9)β the initiator's nameregulatory_pre_cac_allowed(9)β is pre-CAC allowed? asks the question
π INTERNAL REGULATORY DB FUNCTIONS
internal means internal bestie, these are the backstage passes, don't go poking at them in your driver and then act surprised π«Ά
Internal regulatory db functions(9)β section headerreg_query_regdb_wmm(9)β query the regdb for WMMcfg80211_scan_done(9)β scan done, tell everyonecfg80211_sched_scan_results(9),cfg80211_sched_scan_stopped(9),cfg80211_sched_scan_stopped_locked(9)β sched scan results, stopped, and stopped locked (the locked one matters, respect it)cfg80211_inform_bss_frame_data(9)β inform BSS frame datacfg80211_gen_new_bssid(9)β generate a new BSSIDcfg80211_is_element_inherited(9),cfg80211_merge_profile(9)β is the element inherited, and merge the profileenum cfg80211_bss_frame_type(9),cfg80211_get_ies_channel_number(9)β BSS frame type enum and get IEs channel numbercfg80211_ssid_eq(9)β SSID equality checkcfg80211_inform_bss_data(9)β inform BSS data__cfg80211_get_bss(9),cfg80211_get_bss(9)β get BSS, with the double-underscore one being the lower-level sister (mind the underscores, fr fr)cfg80211_ref_bss(9),cfg80211_put_bss(9)β ref it and put it, the classic pairingcfg80211_unlink_bss(9),cfg80211_bss_iter(9)β unlink BSS and BSS itercfg80211_rx_mlme_mgmt(9),cfg80211_auth_timeout(9)β rx MLME mgmt and auth timeoutstruct cfg80211_rx_assoc_resp_data(9),cfg80211_rx_assoc_resp(9)β rx assoc resp data and rx assoc respstruct cfg80211_assoc_failure(9)β hey, that's this page! hi bestie, you are here π (see it in the list, it's self-referential, it's meta, we love that for it)cfg80211_tx_mlme_mgmt(9),cfg80211_rx_unprot_mlme_mgmt(9)β tx MLME mgmt and rx unprotected MLME mgmtcfg80211_michael_mic_failure(9)β Michael MIC failure, the ominous onecfg80211_ibss_joined(9)β IBSS joinedcfg80211_notify_new_peer_candidate(9)β notify a new peer candidate π
π RFKILL INTEGRATION, VENDOR COMMANDS & TEST MODE
the three little side-quest sections, all iconic in their own way:
RFkill integration(9)β section headerwiphy_rfkill_set_hw_state_reason(9)β set the hw state, with a reasonwiphy_rfkill_start_polling(9),wiphy_rfkill_stop_polling(9)β start polling, stop polling, that's the whole bitVendor commands(9)β section headercfg80211_vendor_cmd_alloc_reply_skb(9),cfg80211_vendor_cmd_reply(9)β alloc the reply skb, then replycfg80211_vendor_cmd_get_sender(9)β get the sendercfg80211_vendor_event_alloc(9),cfg80211_vendor_event_alloc_ucast(9),cfg80211_vendor_event(9)β event alloc, unicast alloc, and the event itselfTest mode(9)β section headercfg80211_testmode_alloc_reply_skb(9),cfg80211_testmode_reply(9)β testmode alloc reply skb and replycfg80211_testmode_alloc_event_skb(9),cfg80211_testmode_event(9)β testmode alloc event skb and event
π THE FINAL BOSS: the connect / roam / notify mega-list
no section header here bestie, it just keeps going, and honestly? respect. π₯
struct cfg80211_fils_resp_params(9),struct cfg80211_connect_resp_params(9)β FILS resp params and connect resp paramscfg80211_connect_done(9),cfg80211_connect_bss(9)β connect done and connect BSScfg80211_connect_result(9),cfg80211_connect_timeout(9)β connect result and connect timeoutstruct cfg80211_roam_info(9),cfg80211_roamed(9)β roam info and roamedcfg80211_port_authorized(9),cfg80211_disconnected(9)β port authorized, and the disconnected notificationcfg80211_ready_on_channel(9),cfg80211_remain_on_channel_expired(9),cfg80211_tx_mgmt_expired(9)β ready on channel, remain on channel expired, tx mgmt expiredcfg80211_sinfo_alloc_tid_stats(9),cfg80211_link_sinfo_alloc_tid_stats(9),cfg80211_sinfo_release_content(9)β alloc tid stats, link version of alloc tid stats, and release the contentcfg80211_new_sta(9),cfg80211_del_sta_sinfo(9),cfg80211_del_sta(9)β new sta, del sta sinfo, del stacfg80211_conn_failed(9)β connection failed, the one nobody wants to call πstruct cfg80211_rx_info(9),cfg80211_rx_mgmt_ext(9),cfg80211_rx_mgmt_khz(9),cfg80211_rx_mgmt(9)β rx info, rx mgmt ext, rx mgmt khz, rx mgmtstruct cfg80211_tx_status(9),cfg80211_mgmt_tx_status_ext(9),cfg80211_mgmt_tx_status(9)β tx status, mgmt tx status ext, mgmt tx statuscfg80211_control_port_tx_status(9),cfg80211_rx_control_port(9)β control port tx status and rx control portcfg80211_cqm_rssi_notify(9),cfg80211_cqm_pktloss_notify(9)β CQM RSSI notify and CQM packet loss notifycfg80211_cqm_txe_notify(9),cfg80211_cqm_beacon_loss_notify(9)β CQM TXE notify and CQM beacon loss notify__cfg80211_radar_event(9)β the radar event, dunder included π¨cfg80211_sta_opmode_change_notify(9)β station opmode change notifycfg80211_cac_event(9),cfg80211_background_cac_abort(9)β CAC event and background CAC abortcfg80211_gtk_rekey_notify(9),cfg80211_pmksa_candidate_notify(9)β GTK rekey notify and PMKSA candidate notifycfg80211_rx_spurious_frame(9),cfg80211_rx_unexpected_4addr_frame(9)β spurious frame and unexpected 4-address frame, the "who is this diva" paircfg80211_probe_status(9)β probe statuscfg80211_report_obss_beacon_khz(9),cfg80211_report_obss_beacon(9)β report OBSS beacon, khz flavor and regularstruct cfg80211_beaconing_check_config(9)β beaconing check config, and that's the last one, we made it π
and that's the whole SEE ALSO, every single reference, not one dropped. you're doing amazing sweetie, keep going π
cfg80211_reg_check_beaconing(9)cfg80211_reg_can_beacon(9)cfg80211_reg_can_beacon_relax(9)cfg80211_ch_switch_notify(9)cfg80211_ch_switch_started_notify(9)ieee80211_operating_class_to_band(9)ieee80211_operating_class_to_chandef(9)ieee80211_chandef_to_operating_class(9)ieee80211_chandef_to_khz(9)cfg80211_tdls_oper_request(9)cfg80211_calculate_bitrate(9)
okay bestie the conversion pipeline is right there, we love a glow-up β¨
register, unregister, unregister β it's giving "one of these is not like the other" but honestly they're all load-bearing, no cap π
struct cfg80211_ft_event_params(9)cfg80211_ft_event(9)cfg80211_get_p2p_attr(9)ieee80211_ie_split_ric(9)ieee80211_ie_split(9)ieee80211_fragment_element(9)cfg80211_report_wowlan_wakeup(9)cfg80211_crit_proto_stopped(9)ieee80211_get_num_supported_channels(9)cfg80211_check_combinations(9)cfg80211_iter_combinations(9)cfg80211_get_radio_idx_by_chan(9)cfg80211_stop_link(9)cfg80211_stop_iface(9)cfg80211_shutdown_all_interfaces(9)
not the shutdown-all-interfaces page sitting quietly at the end of the list like it didn't just choose violence π iconic behavior honestly
set and isset, a matched set, we stan a duo π«Ά
cfg80211_free_nan_func(9)struct cfg80211_nan_match_params(9)cfg80211_nan_match(9)cfg80211_nan_func_terminated(9)cfg80211_nan_sched_update_done(9)cfg80211_external_auth_request(9)cfg80211_pmsr_report(9)cfg80211_pmsr_complete(9)cfg80211_iftype_allowed(9)cfg80211_assoc_comeback(9)
the assoc comeback!! literally the sibling of this very page, go give it a read fr fr π
cfg80211_update_owe_info_event(9)cfg80211_bss_flush(9)cfg80211_bss_color_notify(9)cfg80211_obss_color_collision_notify(9)cfg80211_color_change_started_notify(9)cfg80211_color_change_aborted_notify(9)cfg80211_color_change_notify(9)
the whole color-change friend group showed up π started, aborted, plain notify β the way they all pulled up together is so real
cfg80211_6ghz_power_type(9)cfg80211_links_removed(9)struct cfg80211_mlo_reconf_done_data(9)cfg80211_mlo_reconf_add_done(9)cfg80211_schedule_channels_check(9)cfg80211_epcs_changed(9)cfg80211_next_nan_dw_notif(9)cfg80211_nan_cluster_joined(9)cfg80211_nan_ulw_update(9)cfg80211_nan_channel_evac(9)wiphy_locked_debugfs_read(9)wiphy_locked_debugfs_write(9)cfg80211_s1g_get_start_freq_khz(9)cfg80211_s1g_get_end_freq_khz(9)cfg80211_s1g_get_primary_sibling(9)cfg80211_incumbent_signal_notify(9)
and that's the whole list, every last one, nobody left behind π
okay that's a wrap on part three and on the whole page, bestie!! π¦ this one came from ./include/net, dated October 2026, and the page is cfg80211_assoc_failure(9) β go forth, read the sibling pages, and slay your wireless stack debugging ππΈ
π¦ 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