diff options
author | Johannes Berg <johannes.berg@intel.com> | 2010-05-28 15:22:58 +0200 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2010-06-04 15:50:51 -0400 |
commit | 8b9a4e6e442756f670ef507f09bbc6c11dc0fca6 (patch) | |
tree | bed171512423a88dda5125f76568d481acaaabb4 /net/sysctl_net.c | |
parent | 56bf882230d2266a2e07b7f404dc96d157a65daa (diff) | |
download | op-kernel-dev-8b9a4e6e442756f670ef507f09bbc6c11dc0fca6.zip op-kernel-dev-8b9a4e6e442756f670ef507f09bbc6c11dc0fca6.tar.gz |
mac80211: process station blockack action frames from work
Processing an association response could take a bit
of time while we set up the hardware etc. During that
time, the AP might already send a blockack request.
If this happens very quickly on a fairly slow machine,
we can end up processing the blockack request before
the association processing has finished. Since the
blockack processing cannot sleep right now, we also
cannot make it wait in the driver.
As a result, sometimes on slow machines the iwlagn
driver gets totally confused, and no traffic can pass
when the aggregation setup was done before the assoc
setup completed.
I'm working on a proper fix for this, which involves
queuing all blockack category action frames from a
work struct, and also allowing the ampdu_action driver
callback to sleep, which will generally clean up the
code and make things easier.
However, this is a very involved and complex change.
To fix the problem at hand in a way that can also be
backported to stable, I've come up with this patch.
Here, I simply process all aggregation action frames
from the managed interface skb queue, which means
their processing will be serialized with processing
the association response, thereby fixing the problem.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Cc: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/sysctl_net.c')
0 files changed, 0 insertions, 0 deletions