diff options
author | Helmut Schaa <helmut.schaa@googlemail.com> | 2011-08-11 16:17:42 +0200 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2011-08-22 14:45:58 -0400 |
commit | e69deded2bc29e6dd176089252a11b1854012c76 (patch) | |
tree | f20940462acaa806c859d1e7e28ee67bef1cb41b /scripts/cleanfile | |
parent | c1407b6cb22245ae8653cfc195530a9b8eb52879 (diff) | |
download | linux-e69deded2bc29e6dd176089252a11b1854012c76.tar.gz linux-e69deded2bc29e6dd176089252a11b1854012c76.tar.bz2 linux-e69deded2bc29e6dd176089252a11b1854012c76.zip |
mac80211: Tear down BA session on BAR tx failure
As described at [1] some STAs (i.e. Intel 5100 Windows) can end up
correctly BlockAcking incoming frames without delivering them to user
space if a AMPDU subframe got lost and we don't flush the receipients
reorder buffer with a BlockAckReq. This in turn results in stuck
connections.
According to 802.11n-2009 it is not necessary to send a BAR to flush
the recepients RX reorder buffer but we still do that to be polite.
However, assume the following frame exchange:
AP -> STA, AMPDU (failed)
AP -> STA, BAR (failed)
The client in question then ends up in the same situation and won't
deliver frames to userspace anymore since we weren't able to flush
its reorder buffer.
This is not a hypothetical situation but I was able to observe this
exact behavior during a stress test between a rt2800pci AP and a Intel
5100 Windows client.
In order to work around this issue just tear down the BA session as
soon as a BAR failed to be TX'ed.
[1] http://comments.gmane.org/gmane.linux.kernel.wireless.general/66867
Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'scripts/cleanfile')
0 files changed, 0 insertions, 0 deletions