On Thu, 2009-08-06 at 22:34 +0300, Jussi Kivilinna wrote: > Quoting "Johannes Berg" <johannes@xxxxxxxxxxxxxxxx>: > > > On Thu, 2009-08-06 at 21:17 +0300, Jussi Kivilinna wrote: > >> Fix WPA authentication problems by waiting to association to complete. > >> Otherwise userspace (wpa_supplicant) receives authentication packets before > >> association events from driver. > > > >> + /* If we return now, userspace would get association events too late > >> + * (after receiving first packets from access point). This causes > >> + * WPA authentication to fail. > > > > This is a bit weird, shouldn't you just send the event later then? > > > > rndis_wlan bases on rndis_host/usbnet. Problem is that rndis_host uses > polling for rndis_command() results to avoid more complex interrupt > based solution. Because rndis_host and therefore rndis_wlan doesn't > handle interrupts on command channel, rndis_wlan knows about completed > association too late. 'Too late' means here that device starts > receiving packets from AP, which end up ignored because userspace > thinks device isn't assosiated yet (I think). > > So this patch adds waiting in set_essid() and active polling for > association completion in worker. > > Real fix would probably be to hold on data channel until association > is complete, but that would mean touching usbnet/rndis_host little bit > too much than I'd like to. If this patch ever blocks SIOSIWESSID, then a huge NAK. Setting the ESSID is an asynchronous operation, it should *not* block for operation to complete. Completion is signaled only when an IWESSID event is sent to userspace. What you should be doing is dropping packets from the AP on the floor until the firmware things the association is complete. Dan -- 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
