diff options
| author | Aditya Kumar Singh <quic_adisi@quicinc.com> | 2025-01-24 09:16:38 +0300 |
|---|---|---|
| committer | Jeff Johnson <jeff.johnson@oss.qualcomm.com> | 2025-02-04 01:43:28 +0300 |
| commit | 36f002a3e36efd3370f5b6abfc157e7481ecb1e0 (patch) | |
| tree | 63c1261e2b57956d858cb903b124c363356cdad3 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | e26a6989b10a3dfc97b8c206023a6bf3a3ccb94e (diff) | |
| download | linux-36f002a3e36efd3370f5b6abfc157e7481ecb1e0.tar.xz | |
wifi: ath12k: prevent CSA counter to reach 0 and hit WARN_ON_ONCE
Currently, when the driver receives a channel switch count WMI event from
the firmware with a count greater than 1, it calls
ieee80211_beacon_update_cntdwn(). If the beacon transmission fails, the
event will be received again with the previous count value. In this
scenario, the host decrements the mac80211 counter again, causing it to
move ahead of the firmware counter. Ultimately, when the firmware count
reaches 1, the mac80211 counter will reach zero, triggering a
WARN_ON_ONCE(). Therefore, there is a need to check the count value in the
event.
Hence to fix this, maintain the current ongoing counter in arvif. If the
count in the event does not match the expected value, silently discard the
event.
Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20250124-ath12k_mlo_csa-v2-4-420c42fcfecf@quicinc.com
Signed-off-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions