From cba75498f25b6441c39e318f3b36a0723be564ae Mon Sep 17 00:00:00 2001 From: Yeshwanth Sriram Guntuka Date: Wed, 12 Dec 2018 18:22:59 +0530 Subject: [PATCH] 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 --- core/hdd/src/wlan_hdd_hostapd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/core/hdd/src/wlan_hdd_hostapd.c b/core/hdd/src/wlan_hdd_hostapd.c index 51aefb7d220d..805a95c29a29 100644 --- a/core/hdd/src/wlan_hdd_hostapd.c +++ b/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!!");