tree 8b53ef139c9fc90b6064de83c613008af60fe127
parent 34812624dcc0fcbe28caade8077f5464e7d9ee94
author Vamsi Krishna <vamsin@codeaurora.org> 1608312000 +0530
committer Hsiu-Chang Chen <hsiuchangchen@google.com> 1608607947 +0800

nl80211: Do not ignore disconnection event after a connection event

After a disconnect command is issued, wpa_supplicant generates a
disconnection event to self and ignores the next disconnection event
coming from the driver.  In a race condition in which the driver
generates a connected event due to roaming just before receiving the
disconnect command from userspace, wpa_supplicant processes the
connected event after processing the self-generated disconnection event
and enters WPA_COMPLETED state. The driver sends a disconnection event
after processing the disconnect command sent by wpa_supplicant but the
disconnection event is ignored by wpa_supplicant as the disconnection
event is considered to be a result of locally generated disconnect
command. Thus, wpa_supplicant continues to be in the connected
(WPA_COMPLETED) state though the driver is in disconnected state.

Fix this out-of-sync behavior between the driver and wpa_supplicant by
not ignoring the disconnection event from the driver because of the
locally generated disconnect command sent to the driver if there is a
connection event received after issuing the disconnect command to the
driver.

Bug: 170585392
Test: Wifi shows disconnected after leaves AP far away
Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
Change-Id: I363e3e7133d07e98b84d41dac24c4bcd5f2560a3