Adding the flag to mac80211 already without testing was clearly a mistake, one that we now pay for by having to reserve bit 13 forever. The problem is cfg80211 doesn't allow capability/rate changes for station entries that were added unassociated, so the station entries cannot be set up properly when marked associated. Change the NL80211_FEATURE_FULL_AP_CLIENT_STATE value to make it clear to userspace implementations that all current kernels don't actually support it, even though the previous bit is set, and of course also remove the flag from mac80211 until we test and fix the issues.
Showing the changes to include/uapi/linux (1 of 2 files). Show all
Unified · Split
| @@ -3471,8 +3471,9 @@ enum nl80211_feature_flags { · 3470 unmodified lines | ||
| 3471 | 3471 | NL80211_FEATURE_NEED_OBSS_SCAN = 1 << 10, |
| 3472 | 3472 | NL80211_FEATURE_P2P_GO_CTWIN = 1 << 11, |
| 3473 | 3473 | NL80211_FEATURE_P2P_GO_OPPPS = 1 << 12, |
| 3474 | − NL80211_FEATURE_FULL_AP_CLIENT_STATE = 1 << 13, | |
| 3474 | + /* bit 13 is reserved */ | |
| 3475 | 3475 | NL80211_FEATURE_ADVERTISE_CHAN_LIMITS = 1 << 14, |
| 3476 | + NL80211_FEATURE_FULL_AP_CLIENT_STATE = 1 << 15, | |
| 3476 | 3477 | }; |
| 3477 | 3478 | |
| 3478 | 3479 | /** |