4e65e8eab6
In a scenario where the below two HDD commands are executed at the same time from different threads 1. Disconnect which does an RSO Stop and free the pCurRoamProfile 2. Set Blacklist BSSID which does and RSO Update and accessed the pCurRoamProfile pCurRoamProfile is accessed in the function csr_roam_offload_scan after is freed from the other context. The Disconnect command from HDD is protected under the global SME lock, however, the set blacklist BSSID path is not protected under SME lock. There are multiple instances where csr_roam_offload_scan is called without the SME lock which could lead to similar issues. Acquire SME lock before csr_roam_offload_scan from callers in SME/HDD which can be from other threads. Change-Id: I9666bab0001b56ec01dcf1df0becb36344fb6f9a CRs-Fixed: 2226423 |
||
|---|---|---|
| .. | ||
| inc | ||
| src | ||