On Tue, 2009-02-24 at 20:15 +0800, Helmut Schaa wrote: > Am Dienstag, 24. Februar 2009 schrieb Zhu Yi: > > [...] > > > Thanks for the analysis. Are you sure noop_qdisc is still used when we > > are about to netif_carrier_on() after receiving the association success > > response? > > Yes, had a printk in noop_enqueue. > > > From dev_open(), dev_activate() is called after netdev->open. > > So the txq->qdisc_sleeping should be already replaced with pfifo_fast. > > But the state is still DEACTIVATED. > > Right. But for example when a connection cannot be established by ipw2100 > it will call netif_carrier_off on disassociation which in turn leads to a > call to dev_deavtivate. Hence, it is possible that a noop_qdisc is > assigned while the device is up and carrier is off. Make sense. Whatever there is race here but either the driver or the user space is able to control and avoid it. BTW, does wpa_supplicant start to receive EAPOL frames after it gets the association event? [...] > > But in wireless, > > netif_carrier_on() is usually called after an association is succeeded. > > The driver has already some management frames transfered with AP. Now > > it's the time to open the data frame transmission. The driver requires > > to get the activate_dev() result (synchronously or via callback) because > > otherwise the driver has no idea when the Qdisc is ready and then it can > > start to deliver data frames to network stack and user space. > > Exactly. Looks like we didn't bring enough attention for netdev people on this. Should you change the title to remove ipw2100? It should be a generic issue for the current netif_carrier_on/dev_activate() implementation. Thanks, -yi -- 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
