On Fri, 2004-04-02 at 18:40, Mike Anderson wrote: > Greg stopped by and after talking this over I think I see why sd is > racing in its current form. The race happens when sd_remove and do_open > race. Even though I do not like adding a lock_kernel it would appear > adding on to sd_remove would serialize sd_remove and do_open. This would > ensure either do_open's get_gendisk returns a gendisk struct and sd > ref's are incremented or we will start cleaning up and sd_open will not > be called. > > I would believe similar alignment in sr.c to what sd is doing plus > agreement on the lock_kernel should fix both drivers. > > I think the "error out correctly" on trying to get a ref on sdev_gendev > may need some higher serialization as I think there is a race on a release > function starting and the reference count trying to be taken to 1 (i.e. > you need something subsystem wide as you cannot look at the item you > maybe deleting.
I'm not convinced we need any other serialisation. As long as we get the reference we may use the device (of course if the device is being removed and sd_remove is being called, then I/O to it will fail, but I think that's fine). Leaving the user with an open device that won't accept I/O is also fine (as long as it returns the correct error codes). Could you outline what the consequences of this race are? 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
