On Sat, 2010-08-14 at 08:31 +0200, Maxime Bizon wrote: > The driver is still inside ieee80211_register_hw(), but the userspace is > able to create the AP interface before the call is over. Once > wiphy_register() is done, no lock seems to prevent this from happening. > > ieee80211_init_rate_ctrl_alg() then fails with EBUSY, and > ieee80211_register_hw() starts unregistering the phy. > > Is that expected ? Oops. No, not really, but I think the problem is that we do wiphy_register far too early. I think we should see if we can reorder the code in register_hw(). It won't be perfect wrt. debugfs, but I don't think that is a problem. 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
