ieee80211_bss_get_elem(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ ieee80211_bss_get_elem(9) ✨

okay so bestie, welcome to the Kernel API Manual, section 9, and honestly? this one's short and sweet but it's also load-bearing, so pay attention πŸ’…


πŸŽ€ NAME πŸŽ€

ieee80211_bss_get_elem β€” find element with given ID

like, you give it an ID, it finds the element. that's the whole vibe check. no cap πŸ¦‹


✨ SYNOPSIS ✨

const struct element * ieee80211_bss_get_elem (struct cfg80211_bss *bss
, u8 id );

that's the signature, character for character, don't come for me about the line break β€” that's literally how it's written 🫢


🌸 ARGUMENTS 🌸

  • bss β€” the bss to search πŸ‘€ this is the thing you're digging through, bestie. your little treasure chest of elements.
  • id β€” the element ID πŸ” the thing you're looking for inside it. the specific element. the one. main character energy fr fr.

πŸ’– DESCRIPTION πŸ’–

okay so here's the part where you need to actually listen 😭

the return value is an RCU-protected pointer, so rcu_read_lock must be held when calling this function.

that's not a suggestion, that's not a "if you feel like it" β€” that is a hard requirement. hold rcu_read_lock while you call this. periodt. if you don't, you're in undefined-behaviour territory and nobody wants that 🩷

so the whole flow is: you grab the lock, you call ieee80211_bss_get_elem, you do your cute little thing with the element, you let the lock go. iconic behaviour only πŸ™ˆ


⭐ RETURN ⭐

NULL if not found. 🫠

that's it. that's the whole return section. if it's there you get a pointer, if it's not there you get NULL and you gotta deal with it gracefully, bestie β€” no dereferencing NULL, we don't do that here πŸ’€


more coming in part 2, don't go anywhere 🧚

✨ SEE ALSO ✨

okay bestie, this is the part where the page literally name-drops everybody in the cfg80211 friend group 😭 like it's a group-chat roll call and nobody gets left on read. Every single one is here β€” same names, same order, same (9) energy. Let's go 🫢


Actions and configuration β€” the whole getting-stuff-done chapter πŸ’…


Scanning and BSS list handling β€” the section this page's fave actually lives in ✨

  • Scanning and BSS list handling(9), struct cfg80211_ssid(9), struct cfg80211_scan_info(9), struct cfg80211_scan_6ghz_params(9), struct cfg80211_scan_request(9), struct cfg80211_match_set(9), struct cfg80211_sched_scan_plan(9), struct cfg80211_bss_select_adjust(9), struct cfg80211_sched_scan_request(9), enum cfg80211_signal_type(9), struct cfg80211_inform_bss(9), struct cfg80211_bss_ies(9), struct cfg80211_bss(9), ieee80211_bss_get_ie(9) ← yes, the sibling page, go say hi πŸŽ€
  • auth / assoc / connect core: struct cfg80211_auth_request(9), struct cfg80211_assoc_link(9), struct cfg80211_ml_reconf_req(9), enum cfg80211_assoc_req_flags(9), struct cfg80211_assoc_request(9), struct cfg80211_deauth_request(9), struct cfg80211_disassoc_request(9), struct cfg80211_ibss_params(9), struct cfg80211_bss_selection(9), struct cfg80211_connect_params(9), enum cfg80211_connect_params_changed(9), enum wiphy_params_flags(9)
  • PMKSA + wowlan + patterns + qos (the sleepy-time division 😴): struct cfg80211_pmksa(9), struct cfg80211_pkt_pattern(9), struct cfg80211_wowlan_tcp(9), struct cfg80211_wowlan(9), struct cfg80211_coalesce_rules(9), struct cfg80211_coalesce(9), struct cfg80211_wowlan_nd_match(9), struct cfg80211_wowlan_nd_info(9), struct cfg80211_wowlan_wakeup(9), struct cfg80211_gtk_rekey_data(9), struct cfg80211_update_ft_ies_params(9), struct cfg80211_mgmt_tx_params(9), struct cfg80211_dscp_exception(9), struct cfg80211_dscp_range(9), struct cfg80211_qos_map(9)

NAN + PMSR + wiphy structs β€” the deep-lore corner 🧚

  • Neighbor Awareness Networking (NAN)(9), struct cfg80211_nan_band_config(9), struct cfg80211_nan_conf(9), struct cfg80211_nan_channel(9), struct cfg80211_nan_local_sched(9), struct cfg80211_nan_peer_map(9), struct cfg80211_nan_peer_sched(9), enum cfg80211_nan_conf_changes(9), struct cfg80211_nan_func_filter(9), struct cfg80211_nan_func(9)
  • pmk / auth / ftm / pmsr: struct cfg80211_pmk_conf(9), struct cfg80211_external_auth_params(9), struct cfg80211_ftm_responder_stats(9), struct cfg80211_pmsr_ftm_result(9), struct cfg80211_pmsr_result(9), struct cfg80211_pmsr_ftm_request_peer(9), struct cfg80211_pmsr_request_peer(9), struct cfg80211_pmsr_request(9), struct cfg80211_update_owe_info(9), struct mgmt_frame_regs(9)
  • ops + wiphy flags + iface combos: struct cfg80211_ops(9), enum wiphy_flags(9), struct ieee80211_iface_limit(9), struct ieee80211_iface_combination(9), enum wiphy_wowlan_support_flags(9), struct wiphy_wowlan_support(9), struct wiphy_coalesce_support(9), enum wiphy_vendor_command_flags(9), enum wiphy_opmode_flag(9), struct sta_opmode_info(9), struct wiphy_vendor_command(9), struct wiphy_iftype_ext_capab(9), cfg80211_get_iftype_ext_capa(9), struct cfg80211_pmsr_capabilities(9), struct wiphy_iftype_akm_suites(9), struct wiphy_radio_cfg(9), struct wiphy_radio_freq_range(9), struct wiphy_radio(9), enum wiphy_nan_flags(9), struct wiphy_nan_capa(9), struct wiphy(9)

the wiphy lifecycle crew (registration, locking, work queues β€” main character energy πŸ‘‘)


Utility functions β€” the little helpers that ate πŸ’…


Data path helpers πŸ“


Regulatory enforcement infrastructure 🌈


scan/BSS notification + mgmt little icons πŸ¦‹


RFkill integration + Vendor commands + Test mode πŸ’€


connect / roam / disconnect notification besties πŸŽ€


rx/tx mgmt + control port + cqm + radar (the whole notification finale fr fr) πŸ”₯

…and the SEE ALSO list literally does not stop, bestie, it keeps going. Round three, final stretch, no skips 🫢

That's the whole crew, every single one, nobody left behind πŸ’…βœ¨ Go read them, they're all valid, they're all iconic, iykyk.


That's the page, bestie!! πŸŽ€ This little masterpiece lives at ./include/net, dated October 2026, and it's filed under ieee80211_bss_get_elem(9) β€” go forth and get those elements, you absolute legend πŸ‘‘πŸ¦‹πŸ’–

πŸ“¦ where this page comes from