On Tue, Aug 12, 2003 at 07:53:53AM +0100, Christoph Hellwig wrote: > On Tue, Aug 12, 2003 at 12:28:44AM +0200, Andries Brouwer wrote: > > I see an Oops in the SCSI code, caused by the fact that sdkp is NULL > > in sd_shutdown. "How can that be?", you will ask - dev->driver_data was set > > in sd_probe. But in my case sd_probe never finished. An insmod usb-storage > > hangs forever, or at least for more than six hours, giving ample opportunity > > to observe this race between sd_probe and sd_shutdown. > > (Of course sd_probe hangs in sd_revalidate disk.) > > Well, this same problem could show upb in any other driver. Could > you instead send a patch to Pat that the driver model never calls > the shutdown method for a driver that hasn't finished ->probe?
I think it already will not do that due to taking the bus->subsys.rwsem before calling either probe() or remove(). thanks, greg k-h ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
