mirror of
https://git.proxmox.com/git/mirror_ubuntu-kernels.git
synced 2026-01-01 02:27:46 +00:00
a2113cc44d
Consider the following flow:
1. Driver starts to sync the rx queues due to a delba.
mvm->queue_sync_cookie=1.
This rx-queues-sync is synchronous, so it doesn't increment the
cookie until all rx queues handle the notification from FW.
2. During this time, driver starts to sync rx queues due to nssn sync
required.
The cookie's value is still 1, but it doesn't matter since this
rx-queue-sync is non-synchronous so in the notification handler the
cookie is ignored.
What _does_ matter is that this flow increments the cookie to 2
immediately.
Remember though that the FW won't start servicing this command until
it's done with the previous one.
3. FW is still handling the first command, so it sends a notification
with internal_notif->sync=1, and internal_notif->cookie=0, which
triggers a WARN_ONCE.
The solution for this race is to only use the mvm->queue_sync_cookie in
case of a synchronous sync-rx-queues. This way in step 2 the cookie's
value won't change so we avoid the WARN.
The commit in the "fixes" field is the first commit to introduce
non-synchronous sending of this command to FW.
Fixes:
|
||
|---|---|---|
| .. | ||
| binding.c | ||
| coex.c | ||
| constants.h | ||
| d3.c | ||
| debugfs-vif.c | ||
| debugfs.c | ||
| debugfs.h | ||
| ftm-initiator.c | ||
| ftm-responder.c | ||
| fw-api.h | ||
| fw.c | ||
| led.c | ||
| mac80211.c | ||
| mac-ctxt.c | ||
| Makefile | ||
| mvm.h | ||
| nvm.c | ||
| offloading.c | ||
| ops.c | ||
| phy-ctxt.c | ||
| power.c | ||
| quota.c | ||
| rs-fw.c | ||
| rs.c | ||
| rs.h | ||
| rx.c | ||
| rxmq.c | ||
| scan.c | ||
| sf.c | ||
| sta.c | ||
| sta.h | ||
| tdls.c | ||
| testmode.h | ||
| time-event.c | ||
| time-event.h | ||
| tt.c | ||
| tx.c | ||
| utils.c | ||