summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorManish Dharanenthiran <manish.dharanenthiran@oss.qualcomm.com>2026-10-01 14:43:45 +0530
committerJohannes Berg <johannes.berg@intel.com>2026-10-05 15:19:03 +0200
commitbded6f5803dcb83b7ba2153bf9f83535c4066f73 (patch)
tree449874b33357682dcc244c365e21e4abf25f0d04 /include/linux
parentece30e1daf6a9c95d6f9d0518534a0b9c8c7fd42 (diff)
wifi: mac80211: Guard FILS discovery and unsolicited broadcast probe response
According to IEEE Std 802.11-2024, subclause 11.45.2.1 FILS Discovery frame transmission, only a transmitting BSS shall transmit a FILS Discovery frame. Currently, BSS_CHANGED_FILS_DISCOVERY is set unconditionally for all the BSSs. Hence, add a check to allow setting the FILS Discovery flag only for a transmitting BSS. Similarly, IEEE Std 802.11-2024, subclause 26.17.2.3.2 AP behavior for fast passive scanning, mentions that unsolicited broadcast probe response frame shall be transmitted only by a transmitting BSS. Hence, add a check to allow setting the BSS_CHANGED_UNSOL_BCAST_PROBE_RESP only for a transmitting BSS. Currently in user-space there is no restriction on sending this for non-transmitting BSS, thus it may send these for those BSSs as well. While this is not a valid configuration, returning an error here could be fatal because failing 'start_ap' or 'update_ap' operation would result in failure of bringing up those BSSs. Thus, to maintain the compatibility with existing user-space, ignore the config for non-transmitting BSS silently. Signed-off-by: Manish Dharanenthiran <manish.dharanenthiran@oss.qualcomm.com> Link: https://patch.msgid.link/20261001-fils-v3-1-55c5628f9d1d@oss.qualcomm.com Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions