diff options
| author | Dundi Raviteja <dundi@codeaurora.org> | 2018-10-04 15:22:56 +0530 |
|---|---|---|
| committer | Gerrit - the friendly Code Review server <code-review@localhost> | 2018-10-07 22:34:56 -0700 |
| commit | 08a1cf7d52fb56981efa02e5edb0b78ef70a6a59 (patch) | |
| tree | 83b6362dbdaf61310038723b434f90a55382b26c /scripts/gdb/linux/tasks.py | |
| parent | a41b4260bec87720c62d531b1eb49a350ab41b4e (diff) | |
qcacld-3.0: Validate context before allocating memory for sme_config
Currently in function __iw_setint_getnone(), allocating memory for
sme_config before validating hdd context.
In the process of recovery, hdd_wlan_stop_modules() set qdf domain
to QDF_MEM_DOMAIN_INIT and in hdd_wlan_start_modules() it is again
set to QDF_MEM_DOMAIN_ACTIVE. Now, if __iw_setint_getnone() is
triggered, hdd context validation fails because of recovery is in
progress and try to free memory allocated for sme_config.
If __iw_setint_getnone() is triggered just before setting qdf domain
to QDF_MEM_DOMAIN_ACTIVE, allocates memory for sme_config and if
hdd_wlan_start_modules() set qdf domain to QDF_MEM_DOMAIN_ACTIVE
just after allocating memory to sme_config, while freeing qdf domain
status will be mismatch and may cause panic.
To address this, in __iw_setint_getnone() validate hdd context before
allocating memory for sme_config.
Change-Id: I6d0a7fa5f0752bd9b0c858c3c20eefee307ad85d
CRs-Fixed: 2324484
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions