Browse Source

qcacld-3.0: Send failure code in start_ap return path on failure

Start_ap failure due to no vdev start response is indicated
to supplicant using wext event instead of sending the
proper error code in return path of start_ap API. This
results in supplicant ending up in ap-enabled state since
wext events are not handled by supplicant.

Fix is to send the error code in return path of start_ap API
instead of sending wext event to indicate start AP failure.

Change-Id: I1c65aa65641c0ab718c734bd815ef790b1dfa636
CRs-Fixed: 2369681
Yeshwanth Sriram Guntuka 6 years ago
parent
commit
cba75498f2
1 changed files with 2 additions and 1 deletions
  1. 2 1
      core/hdd/src/wlan_hdd_hostapd.c

+ 2 - 1
core/hdd/src/wlan_hdd_hostapd.c

@@ -5418,7 +5418,8 @@ int wlan_hdd_cfg80211_start_bss(struct hdd_adapter *adapter,
 
 	wlansap_reset_sap_config_add_ie(pConfig, eUPDATE_IE_ALL);
 
-	if (!QDF_IS_STATUS_SUCCESS(qdf_status)) {
+	if (!QDF_IS_STATUS_SUCCESS(qdf_status) ||
+	    !QDF_IS_STATUS_SUCCESS(hostapd_state->qdf_status)) {
 		mutex_unlock(&hdd_ctx->sap_lock);
 
 		hdd_err("qdf wait for single_event failed!!");