Re: [PATCH 4/4] ath6kl: Fix random reconnect failures

[Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>]

On Sat, Sep 10, 2011 at 03:26:37PM +0530, Vasanthakumar Thiagarajan wrote:
> Sometimes connect events are received after disconnect
> events from target, this puts host and target in different
> states. When receiving a connect event in a wrong state,
> make sure to send disconnect event to target to maintain
> state consistency.
> 
> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
> ---
>  drivers/net/wireless/ath/ath6kl/cfg80211.c |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/net/wireless/ath/ath6kl/cfg80211.c b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> index 0ad458b..2e4bea3 100644
> --- a/drivers/net/wireless/ath/ath6kl/cfg80211.c
> +++ b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> @@ -460,6 +460,14 @@ void ath6kl_cfg80211_connect_event(struct ath6kl *ar, u16 channel,
>  				   "%s: ath6k not in station mode\n", __func__);
>  			return;
>  		}
> +
> +		if ((ar->sme_state != SME_CONNECTING) &&
> +		    (ar->sme_state != SME_CONNECTED)) {
> +			ath6kl_dbg(ATH6KL_DBG_WLAN_CFG,
> +				   "Connect event at inappropriate state, sending disconnect cmd\n");
> +			ath6kl_wmi_disconnect_cmd(ar->wmi);
> +			return;
> +		}

Please hold on this patch, it seems to introduce regression when
testing with different APs.

Vasanth