On Wednesday 30 July 2008 19:13:52 Herton Ronaldo Krzesinski wrote: > > Yeah, I said exactly that. > > You protect the loopback stuff. Not any config callback or anything else. > > Ah ok, only protect the section, like this? Yeah, well. In theory, yes. In practice: Aren't there other races possible, too? I mean even races with other parts of the driver. b43 needs to take the global driver mutex in the conf callback to make sure nothing changes (device init state probably is the most important one. Device going down while configuring would be a fatal crash). So in b43 we have a global mutex which protects everything (all data and all device state), except the data and state that's accessed in the IRQ paths. (We have more locks for shared device memory and so on... But these are nested inside of the mutex or the IRQ state lock) -- Greetings Michael. -- 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
