diff options
author | Alexander Wetzel <alexander@wetzel-home.de> | 2022-12-30 13:18:49 +0100 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2023-01-10 13:24:12 +0100 |
commit | 4444bc2116aecdcde87dce80373540adc8bd478b (patch) | |
tree | 3dd34af4a436d1feca6c6f1045033bd54cfa1dda /net/bridge/br_mdb.c | |
parent | e66b7920aa5ac5b1a1997a454004ba9246a3c005 (diff) | |
download | linux-stable-4444bc2116aecdcde87dce80373540adc8bd478b.tar.gz linux-stable-4444bc2116aecdcde87dce80373540adc8bd478b.tar.bz2 linux-stable-4444bc2116aecdcde87dce80373540adc8bd478b.zip |
wifi: mac80211: Proper mark iTXQs for resumption
When a running wake_tx_queue() call is aborted due to a hw queue stop
the corresponding iTXQ is not always correctly marked for resumption:
wake_tx_push_queue() can stops the queue run without setting
@IEEE80211_TXQ_STOP_NETIF_TX.
Without the @IEEE80211_TXQ_STOP_NETIF_TX flag __ieee80211_wake_txqs()
will not schedule a new queue run and remaining frames in the queue get
stuck till another frame is queued to it.
Fix the issue for all drivers - also the ones with custom wake_tx_queue
callbacks - by moving the logic into ieee80211_tx_dequeue() and drop the
redundant @txqs_stopped.
@IEEE80211_TXQ_STOP_NETIF_TX is also renamed to @IEEE80211_TXQ_DIRTY to
better describe the flag.
Fixes: c850e31f79f0 ("wifi: mac80211: add internal handler for wake_tx_queue")
Signed-off-by: Alexander Wetzel <alexander@wetzel-home.de>
Link: https://lore.kernel.org/r/20221230121850.218810-1-alexander@wetzel-home.de
Cc: stable@vger.kernel.org
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/bridge/br_mdb.c')
0 files changed, 0 insertions, 0 deletions