wifi: mt76: unlink TWT flows when MCU ADD fails
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | wifi: mt76: mt7915: unlink TWT flow on MCU add failuredrivers/ | +3 | 0 replies | |
| 2/2 | wifi: mt76: mt7996: unlink TWT flow on MCU add failuredrivers/ | +3 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] wifi: mt76: unlink TWT flows when MCU ADD fails
mt7915 and mt7996 link a TWT flow into the device list before asking the MCU to add the agreement. If that request fails, the accounting masks remain clear but the embedded flow node stays linked.
A retry can corrupt the list by reinitializing the same linked node. If the station is removed instead, the mask-gated teardown skips the flow, leaving a dangling node for later scheduling and debugfs walks. The two patches restore the list to its pre-request state on the MCU ADD failure path, split per driver because their Fixes targets differ.
MCU DELETE failures are deliberately outside this series. Deciding whether to drop host bookkeeping while firmware may retain an agreement requires separate ownership and accounting treatment.
Zhao Li (2):
wifi: mt76: mt7915: unlink TWT flow on MCU add failure
wifi: mt76: mt7996: unlink TWT flow on MCU add failure
drivers/net/wireless/mediatek/mt76/mt7915/mac.c | 4 +++- drivers/net/wireless/mediatek/mt76/mt7996/mac.c | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-)
base-commit: 57aa1718d5953dd532137d43b696c68545c2e0b3
Signature · 1 line
2.50.1 (Apple Git-155)