Michal Schmidt wrote: > Dan Williams wrote: >> Wow, that's somewhat ugly. Do other drivers just not have this problem, >> or have they worked around it in similar or different ways? Just trying >> to understand if the scope of the issue is wider than just airo. > > For instance, drivers/net/wireless/atmel.c looks very similar, so I > guess it has the same race. With airo the race is just more visible, > because of all the long sleeps it does between getting the name with > dev_alloc_name and finally registering it. > > eepro100.c takes rtnl_lock to avoid the issue. So does ns83820.c - it > has a big comment about how ugly it is. A cleaner way would be to do most of the initialization later, from the ->open() method. I'll explore how workable this approach would be. Michal - 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
