cfg80211_ve...oc_reply_skb(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so this is the cfg80211_vendor_cmd_alloc_reply_skb(9) page from the Kernel API Manual — yes, the name is a whole mouthful, but it's literally the function that allocates a vendor command reply ✨🫶

cfg80211_vendor_cmd_alloc_reply_skb — allocate vendor command reply 💅

✨ SYNOPSIS ✨

struct sk_buff * cfg80211_vendor_cmd_alloc_reply_skb (struct wiphy
*wiphy , int approxlen );

🎀 ARGUMENTS 🎀

  • wiphy — the wiphy. that's it, that's the whole vibe 🌈
  • approxlen — an upper bound of the length of the data that will be put into the skb. so it's the max size you're planning to put in there, bestie 🍓

💜 DESCRIPTION 💜

This function allocates and pre-fills an skb for a reply to a vendor command. Since it is intended for a reply, calling it outside of a vendor command's doit operation is invalid. 🚨 no cap, that part is serious: doit only.

The returned skb is pre-filled with some identifying data in a way that any data that is put into the skb (with skb_put, nla_put or similar) will end up being within the NL80211_ATTR_VENDOR_DATA attribute. so all that needs to be done with the skb is adding data for the corresponding userspace tool, which can then read that data out of the vendor data attribute. 🦋✨

You must not modify the skb in any other way. like, don't touch it, don't redecorate it, don't give it a makeover — just add your data and go 💅

When done, call cfg80211_vendor_cmd_reply with the skb and return its error code as the result of the doit operation. 👑

👑 RETURN 👑

An allocated and pre-filled skb. NULL if any errors happen. 💖

✨ SEE ALSO ✨

okay bestie, this is the part where the page hands you the whole friend group 💅 like, every single cross-reference cfg80211 has ever vibed with, all 359 of them, in the original order because we do NOT shuffle the group chat. no cap, this list is long. hydrate first 🍓

that's the capability-girlie block, we love her 🌸

configuration section ate and left no crumbs fr fr 👑

  • 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_elem(9)
  • ieee80211_bss_get_ie(9)
  • 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)
  • 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)

scanning bestie really said "let me look at every single BSS" and honestly? iconic 🔍

the whole wiphy lifecycle is here, from wiphy_new(9) to wiphy_free(9) — it's giving birth-to-death storyline 😭🦋

utility functions girlies stay winning, they do all the actual work ngl 💪✨

regulatory bestie is the strict parent of the group and honestly we need her 🚨👑

lowkey the move here is man whatever name you actually need instead of reading this wall of text, but the fact that every single one of these is one man 9 <name> away? that's a serve 💅

and that's the whole cross-reference gang, every last one of them, nothing cut, nothing merged, nothing "fixed" — and there's still more page coming, so don't you dare close the tab yet bestie 🫶

okay so the SEE ALSO list keeps going — and honestly it keeps going, like the group chat when someone asks "what's the wifi password" 😭 so here's the rest, all of it, no skips, no shortcuts ✨

and that's the whole list, every single one, accounted for 🫶 like yeah it's a lot but that's just how the wireless stack is, she's thorough 💅

aaaand that's a wrap on the page!! 🎀 this whole thing lives out of ./include/net, dated October 2026, and it's the man page for cfg80211_ve...oc_reply_skb(9) — go forth and read the source bestie, you got this 🌈💖

📦 where this page comes from