diff options
| author | Ashish Kumar Dhanotiya <adhanoti@codeaurora.org> | 2018-03-22 14:41:10 +0530 |
|---|---|---|
| committer | nshrivas <nshrivas@codeaurora.org> | 2018-03-23 02:54:55 -0700 |
| commit | 79bd0aae080d7fe8eaf15c1c4a0a26178792b4fe (patch) | |
| tree | 14f994f2f2235512f14be3763673d848f76f149b /tools/perf/scripts/python | |
| parent | e360a22c135349df391a41d71a279501cdf68543 (diff) | |
qcacld-3.0: Complete all wait events before shutdown
There is a race condition between complete wait events as part of fw_down
indication and wait for timeout of stop_bss_event during stop_ap.
When stop ap and SSR runs parallel, first as part of SSR, fw_down
indication comes and all the wait_events are getting set. After this
as part of SAP stop, driver is waiting for stop_bss_event which will
be never set as fw_down indication is already processed. Timeout of
stop_bss_event is much higher than the timeout of wait-for-external-
thread-completion during shutdown, hence shutdown will proceed without
setting the stop_bss_event. Now as part of the SSR, hdd_re_init gets
invoked and the memory of the hdd_hostapd_state (and as part of this
memory of stop_bss_event) is getting memset inside hdd_init_ap_mode.
After this memset the timeout of the stop_bss_event occurs and
stop_bss_event tries to access this memset memory.
To address this issue, all the events which were added in between fw_down
indication and shutdown process, should be completed as part of
the shutdown.
Change-Id: I022f125b2afc99862351407b140f2d1b72f43bc4
CRs-Fixed: 2206326
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
