瀏覽代碼

qcacld-3.0: Don't take psoc lock while check for objmgr leaks

While forcefully releasing the reference leaks driver is taking a
psoc lock and forcefully releasing the object references, which
in turn try to acquire the same lock resulting in deadlock.

Don't take psoc lock while forcefully releasing the psoc lock.

Change-Id: I25d2c84f66927888220ecd61e7fa5c6137002069
CRs-Fixed: 3414339
Arun Kumar Khandavalli 2 年之前
父節點
當前提交
04460763ae
共有 1 個文件被更改,包括 0 次插入2 次删除
  1. 0 2
      core/hdd/src/wlan_hdd_main.c

+ 0 - 2
core/hdd/src/wlan_hdd_main.c

@@ -3770,7 +3770,6 @@ static void hdd_check_for_objmgr_leaks(struct hdd_context *hdd_ctx)
 	if (!psoc)
 		return;
 
-	wlan_psoc_obj_lock(psoc);
 
 	hdd_check_for_objmgr_peer_leaks(psoc);
 
@@ -3794,7 +3793,6 @@ static void hdd_check_for_objmgr_leaks(struct hdd_context *hdd_ctx)
 		wlan_objmgr_for_each_refs(ref_id_dbg, ref_id, refs)
 			wlan_objmgr_pdev_release_ref(pdev, ref_id);
 	}
-	wlan_psoc_obj_unlock(psoc);
 }
 
 static void hdd_check_for_leaks(struct hdd_context *hdd_ctx, bool is_ssr)