qcacld-3.0: Don't send RSO update after receiving set pmksa command

When set_pmksa command is received from userspace, the internal
pmk table is updated with the new bssid entry and the pmk is saved
to the session. Additionally this update triggers an RSO update
command to the firmware which causes the use of stale pmk for
single pmkid case, in which the BSS capability of SAE single pmk
will be known only after parsing the beacon/probe received in the
roam synch indication.

So donot send RSO update on receiving set pmksa command.

Change-Id: I25419fbc3061ab963ccf3228b3681c83773a7963
CRs-Fixed: 2659055
This commit is contained in:
Pragaspathi Thilagaraj
2020-04-09 01:05:32 +05:30
committed by nshrivas
parent 67a40617b6
commit ecec2d5b28
8 changed files with 228 additions and 91 deletions

View File

@@ -980,14 +980,6 @@ ucfg_mlme_get_delay_before_vdev_stop(struct wlan_objmgr_psoc *psoc,
return QDF_STATUS_SUCCESS;
}
#if defined(WLAN_SAE_SINGLE_PMK) && defined(WLAN_FEATURE_ROAM_OFFLOAD)
void ucfg_mlme_update_sae_single_pmk_info(struct wlan_objmgr_vdev *vdev,
struct mlme_pmk_info *sae_single_pmk)
{
wlan_mlme_update_sae_single_pmk(vdev, sae_single_pmk);
}
#endif
QDF_STATUS
ucfg_mlme_get_roam_bmiss_final_bcnt(struct wlan_objmgr_psoc *psoc,
uint8_t *val)