diff options
| author | Ilan Peer <ilan.peer@intel.com> | 2014-02-25 15:33:38 +0200 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2014-02-25 17:34:18 +0100 |
| commit | 7c8d5e03acc680eb433b0d5dbacbb6cc9db663a1 (patch) | |
| tree | 59b267fcc15a04dcd69c9e3c45e5d51f0fe745c0 /net/wireless/core.c | |
| parent | 31559f35c5724976fd975e5d7e90cdb693b8dd27 (diff) | |
| download | blackbird-op-linux-7c8d5e03acc680eb433b0d5dbacbb6cc9db663a1.tar.gz blackbird-op-linux-7c8d5e03acc680eb433b0d5dbacbb6cc9db663a1.zip | |
cfg80211: send stop AP event only due to internal reason
Commit "nl80211: send event when AP operation is stopped" added an
event to notify user space that an AP interface has been stopped, to
handle cases such as suspend etc. The event is sent regardless
if the stop AP flow was triggered by user space or due to internal state
change.
This might cause issues with wpa_supplicant/hostapd flows that consider
stop AP flow as a synchronous one, e.g., AP/GO channel change in the
absence of CSA support. In such cases, the flow will restart the AP
immediately after the stop AP flow is done, and only handle the stop
AP event after the current flow is done, and as a result stop the AP
again.
Change the current implementation to only send the event in case the
stop AP was triggered due to an internal reason.
Signed-off-by: Ilan Peer <ilan.peer@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/wireless/core.c')
| -rw-r--r-- | net/wireless/core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/net/wireless/core.c b/net/wireless/core.c index 76ae6a605abb..276cf938f764 100644 --- a/net/wireless/core.c +++ b/net/wireless/core.c @@ -783,7 +783,7 @@ void cfg80211_leave(struct cfg80211_registered_device *rdev, break; case NL80211_IFTYPE_AP: case NL80211_IFTYPE_P2P_GO: - cfg80211_stop_ap(rdev, dev); + cfg80211_stop_ap(rdev, dev, true); break; default: break; |
