diff options
| author | Ganapathi Bhat <gbhat@marvell.com> | 2018-08-21 13:23:01 +0530 |
|---|---|---|
| committer | Kalle Valo <kvalo@codeaurora.org> | 2018-08-31 18:46:53 +0300 |
| commit | 7bd4628c2f31c51254aa39628ecae521d00d0b90 (patch) | |
| tree | 9ada4404ce1058d7c1403d87fea6e6572fde0580 /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 199ba9faca909e77ac533449ecd1248123ce89e7 (diff) | |
| download | linux-7bd4628c2f31c51254aa39628ecae521d00d0b90.tar.gz linux-7bd4628c2f31c51254aa39628ecae521d00d0b90.zip | |
mwifiex: do no submit URB in suspended state
There is a possible race between USB suspend and main thread:
1. After processing the command response, main thread will submit
rx_cmd URB back so as to process next command response, by
calling mwifiex_usb_submit_rx_urb.
2. During USB suspend, the suspend handler will check if rx_cmd
URB is pending(submitted) and if true, kill this URB.
There is a possible race between #1 and #2, where rx_cmd URB will
be submitted by main thread(#1) after the suspend handler check
in #2.
To fix this, check if device is already suspended in
mwifiex_usb_submit_rx_urb, in which case do not submit the URB.
Signed-off-by: Vidya Dharmaraju <vidyad@marvell.com>
Signed-off-by: Cathy Luo <cluo@marvell.com>
Signed-off-by: Ganapathi Bhat <gbhat@marvell.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions
