summaryrefslogtreecommitdiff
path: root/ipc
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2014-05-14 15:34:41 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-06-07 13:25:31 -0700
commitd13ab64e7a9b68da0c1354085e2277778026b86a (patch)
treeccd2fee35f60ec3bb09fe942ac62948fe16370f7 /ipc
parented32bcbb8d5711286f7e4944968a3dfa49c1d1ab (diff)
downloadlinux-3.10-d13ab64e7a9b68da0c1354085e2277778026b86a.tar.gz
linux-3.10-d13ab64e7a9b68da0c1354085e2277778026b86a.tar.bz2
linux-3.10-d13ab64e7a9b68da0c1354085e2277778026b86a.zip
mac80211: fix on-channel remain-on-channel
commit b4b177a5556a686909e643f1e9b6434c10de079f upstream. Jouni reported that if a remain-on-channel was active on the same channel as the current operating channel, then the ROC would start, but any frames transmitted using mgmt-tx on the same channel would get delayed until after the ROC. The reason for this is that the ROC starts, but doesn't have any handling for "remain on the same channel", so it stops the interface queues. The later mgmt-tx then puts the frame on the interface queues (since it's on the current operating channel) and thus they get delayed until after the ROC. To fix this, add some logic to handle remaining on the same channel specially and not stop the queues etc. in this case. This not only fixes the bug but also improves behaviour in this case as data frames etc. can continue to flow. Reported-by: Jouni Malinen <j@w1.fi> Tested-by: Jouni Malinen <j@w1.fi> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions