On Thu, Jun 13, 2019 at 09:46:59PM +0530, Amit Khatri wrote: > if driver stuck in connection and not able to clear > wdev->conect_keys in cfg80211 layer.below error comes > at wpa_supplicant. > nl80211: MLME connect failed: ret=-115 (Operation now in progress) > This happens because cfg layer return 115 after chceking wdev->connect_keys. > now connct command will never reach to driver. > there is one way to clear wdev->connect_keys call > wpa_driver_nl80211_disconnect() explicitly and try to make connection. Could you please clarify how a driver can get in this state? Would you have an example wpa_supplicant debug log showing a case where this happens? The only case where I can see cfg80211.c return -EINPROGRESS based on wdev->connect_keys being set is in cfg80211_connect() where the comment implies the driver is in the process of connecting with WEP. Shouldn't the driver be finishing that attempt at latest based on some kind of timeout if there is an unexpected failure? Why would wpa_supplicant need to have workaround code for trying to recover from something that sounds like a driver issue? -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
