qcacld-3.0: Use same sap_context for different SAP wrongly

When receive dfs event, if no available channel,  stop all AP,
but send eSAP_STOP_BSS_DUE_TO_NO_CHNL to same AP for 2 times
wrongly during SAP+SAP concurrency, init and schedule same work
queue sap_stop_bss_work 2 times at nearly same time, deadlock
happens

Change-Id: I86cf0ed578e81b3bc1941e057e91c9d952893e07
CRs-Fixed: 2230873

core/sap/src/sap_api_link_cntl.c

@@ -1075,7 +1075,7 @@ wlansap_roam_callback(void *ctx, struct csr_roam_info *csr_roam_info,
 					  QDF_TRACE_LEVEL_ERROR,
 					  FL("sapdfs: no available channel for sapctx[%pK], StopBss"),
 					  pSapContext);
-				sap_signal_hdd_event(sap_ctx, NULL,
+				sap_signal_hdd_event(pSapContext, NULL,
 					eSAP_STOP_BSS_DUE_TO_NO_CHNL,
 					(void *) eSAP_STATUS_SUCCESS);
 			}