summaryrefslogtreecommitdiff
path: root/drivers/net/wireless/wl3501_cs.c
diff options
context:
space:
mode:
authorBenjamin Berg <benjamin.berg@intel.com>2024-02-18 19:51:47 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-03-28 21:59:02 +0100
commit4903303f25f48b5a1e34e6324c7fae9ccd6b959a (patch)
tree409269b8638826e87eb6fa164bf006cd681c92d4 /drivers/net/wireless/wl3501_cs.c
parent406a037d93b769bca248476bd14bbe548dc1ec35 (diff)
downloadlinux-4903303f25f48b5a1e34e6324c7fae9ccd6b959a.tar.gz
linux-4903303f25f48b5a1e34e6324c7fae9ccd6b959a.tar.bz2
linux-4903303f25f48b5a1e34e6324c7fae9ccd6b959a.zip
wifi: iwlwifi: mvm: ensure offloading TID queue exists
commit 78f65fbf421a61894c14a1b91fe2fb4437b3fe5f upstream. The resume code path assumes that the TX queue for the offloading TID has been configured. At resume time it then tries to sync the write pointer as it may have been updated by the firmware. In the unusual event that no packets have been send on TID 0, the queue will not have been allocated and this causes a crash. Fix this by ensuring the queue exist at suspend time. Signed-off-by: Benjamin Berg <benjamin.berg@intel.com> Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com> Link: https://msgid.link/20240218194912.6632e6dc7b35.Ie6e6a7488c9c7d4529f13d48f752b5439d8ac3c4@changeid Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Jianqi Ren <jianqi.ren.cn@windriver.com> Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/net/wireless/wl3501_cs.c')
0 files changed, 0 insertions, 0 deletions