On Sun, 2004-04-04 at 22:17, Alan Stern wrote: > On 4 Apr 2004, James Bottomley wrote: > > On Sun, 2004-04-04 at 12:46, Alan Stern wrote: > > > Ah, you have left out the third, bad alternative: open succeeds, user gets > > > an fd that points to a deallocated device. More details below... > > > > No, that would be a bug. > > Of course it would! That's exactly what this thread is about: bugs caused > by improper handling of open/disconnect races.
So you're quietly shifting your ground away from this assertion: On Sat, 2004-04-03 at 19:40, Alan Stern wrote: > The problem _can_ be solved by introducing a lock higher up, such as at > the driver level or at the bus level. (A kernel lock would work too but > it would be extravagantly excessive.) For example, the bus subsystem > rwsem in the driver model prevents analogous problems there. But you > don't want to get a read lock on a bus-wide semaphore every time your > open() procedure runs! A driver-wide lock makes a good solution. > > Another possible solution would be to have disconnect() perform an RCU > update to the device pointer. I haven't seen any code that does this, but > I think it ought to work. ? My contention is that the races can be solved by proper refcounting (without the need for locks and RCUs) not that we don't have any bugs in sd.c (I'll be happy if I can pull them all out of sr at the moment). James ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
