On 02/26/2014 10:37 AM, Johannes Berg wrote: > On Wed, 2014-02-26 at 10:28 +0100, Arend van Spriel wrote: > >>> Yes. Can't we just flush the work at some strategic place? >>> >>> Actually you're not talking about the "disconnect_work" (which is >>> related to regulatory) but the "event_work" so I was confused here for a >>> second. >>> >>> What was the warning? cfg80211 already calls >>> cfg80211_process_wdev_events() from within the REMOVE netdev notifier, >>> so that *shouldn't* have happened. >> >> I guess that means some wdev event is missing? It was the >> WARN_ON(current->bss) that fired. > > Hmm, that's odd, the process_wdev_events() call is right before that, so > I don't see how that could have happened? Ok. The warning probably happened in earlier kernel, because our module exit was buggy. I fixed that a while ago and I just verified I don't see it without this patch. Sorry for bringing that diversion up. Actually, this was not the reason for the doing the msleep(). The problem was that wpa_supplicant received RTM_DELLINK, before getting the NL08211_DISCONNECT. This resulted in RTM_DELLINK, immediately followed by RTM_ADDLINK, followed by NL80211_DISCONNECT. Gr. AvS -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
