diff options
| author | Aloka Dixit <aloka.dixit@oss.qualcomm.com> | 2026-10-02 12:10:56 -0700 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2026-10-05 15:19:15 +0200 |
| commit | 56fb2334c86cef0b6d44099a6b21de4c8d80a7cb (patch) | |
| tree | ad4b5181555711e3fa1d3e71c2d17f28ccc66899 /include/linux | |
| parent | bded6f5803dcb83b7ba2153bf9f83535c4066f73 (diff) | |
Revert "wifi: mac80211: do not use old MBSSID elements"
Commit a519be2f5d95 ("wifi: mac80211: do not use old MBSSID
elements") fixed the incorrect inclusion of stopped/removed
non-transmitted profiles from the Beacon frames, but it caused
a regression for channel switch (CSA) and BSS color change (CCA)
operations initiated from hostapd.
Hostapd passes two Beacon templates to kernel for CSA and CCA -
(1) beacon_csa/beacon_color_change used during the countdown.
(2) beacon_after/beacon_next used after the countdown completes.
Hostapd relies on the kernel to include the old MBSSID elements
while sending beacon_csa/beacon_color_change templates to the
driver.
This path is now broken and results in CSA/CCA failure.
Including existing MBSSID elements explicitly makes the netlink
buffer larger than default 4 KB depending on the number of APs
which would need unnecessary complication to pre-calculate the
buffer length.
Revert the commit to fix the regression.
Regarding the original issue fixed by the reverted commit -
Hostapd now has a new commit which always includes at least one
MBSSID element when the feature is enabled, hence when all
non-transmitted profiles are removed, this empty element ensures
that stopped profiles are not advertised.
Fixes: a519be2f5d95 ("wifi: mac80211: do not use old MBSSID elements")
Signed-off-by: Aloka Dixit <aloka.dixit@oss.qualcomm.com>
Link: https://patch.msgid.link/20261002-csa_cca_fix-v1-1-b83a998aeb44@oss.qualcomm.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
