On Wed, 2010-09-29 at 10:16 -0700, Luis R. Rodriguez wrote: > > 2. NL80211_CMD_ASSOCIATE to newly authenticated AP from user space > > > > - Clean up any existing BA session with an AP, if any. > > Here the assumption is, ieee80211_work_work() has already > > configured the device back to it's operating channel (the > > old one) after the authentication is complete with the new > > AP. This should have happened part of 1. > > - Start the association process with the new AP. > > No see, I believe we actually get the association response and *then* > we teardown the BA agreements. Let me review this some more today. No, Vasanth's right, but there's a race: * we go off-channel * we send auth * we get auth * we notify wpa_s * wpa_s asks for assoc | these aren't ordered * we disassoc | quite right but it's * we return from off-channel | hard to avoid ... * we assoc to new AP johannes -- 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
