On Fri, 3 Jan 2003, Nate Lawson wrote: NL>I was looking into some "could sleep messages" and found some bogus NL>locking in the attach routine of many drivers. Several init a mtx in NL>their softc and then lock/unlock it in their attach routine. This, of NL>course, does nothing to provide exclusive access to a device. I assume NL>there is going to be a global IF_LOCK or something to be used in attach NL>routines. Can someone fill me in on the intended design?
Probably not. I asked the same question a couple of month ago and got 0 answers. I think, there is no way, the driver itself can assure exclusive access to the device it is attaching. It *must* assume, that there is some kind of locking around the call to the attach routine. Getting the lock in the softc inside the attach routine may be neccessary, because the routine may call other functions that assume they have the lock. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
