On Thu, 2010-08-12 at 20:42 +0200, Johannes Berg wrote: > Err, it was merged a long time ago I'm hitting another race now, it appeared after I disabled CONFIG_CRYPTO_MANAGER_TESTS (new option in 2.6.35.2). I have a userspace daemon that listen for new phy event, and create and configure an AP interface just after it gets the event. 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 ? I was able to get past it by taking rtnl lock before wiphy_register() -- Maxime -- 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
