diff options
| author |   Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2026-05-13 17:06:27 +0300 |
|---|---|---|
| committer |   Johannes Berg <johannes.berg@intel.com> | 2026-05-20 11:14:41 +0200 |
| commit | e1e83feb8eae82cc9cc676db4c70f52fedc4735d (patch) | |
| tree | b9a5c7b28be93545c9372696fa101c146a762a7a /tools/testing/selftests/dm-verity/git:/ssh:/git@git.zx2c4.com | |
| parent | wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs (diff) | |
wifi: mac80211: don't override max_amsdu_subframes
In client mode, the extended capabilities are handled by the kernel
looking at the association frame. When the supplicant installs the keys
it calls sta_apply_parameters and it doesn't include the extended
capabilities since those can't change after association.
As a result, we overrode the max_amsdu_subframes that we set after
association.
Check that the ext_capa coming from the user space is valid before
looking at it. If the ext_capa is NULL, it really means that the
extended capabilities are not changed (as opposed to cleared).
The default value for max_amsdu_subframes is 0, which means there is no
limit. This value is valid and in case the association response frame
does not have extended capabilities, this is the value we should use.
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221079
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Reviewed-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20260513170623.828dbb58c782.Ifd2bfc190c26140e919127adb02ffddd7b551499@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'tools/testing/selftests/dm-verity/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions