On Wed, Feb 26, 2003 at 02:02:05PM +0100, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Feb 25, 2003 at 01:22:10PM -0800, Greg KH wrote: > > Ick, no, I don't like this. I think the scanner driver can actually get > > rid of all of these horrible locks to handle the disconnect/close mess > > by just using a reference count. To back this up, here's a patch that I > > just wrote for the scanner driver (it's on top of the two other patches > > you sent me) that adds a kobject and should handle the destruction of > > the device just fine when the last reference goes away. > > kobject is nice but that won't help for 2.4 because there is no > kobject in 2.4 (right?). Or do i miss something? The idea was to find a > solution for the 2.4 crashes but test in 2.5 fisrt :-) > > Or should I write a replacement for kobject for the 2.4 scanner driver?
If we get this working, a small kobject replacement in 2.4 that handles reference counting and destruction is quite simple. > Well, the patch compiles and I can scan. Looks like the scn object is > freed after (disconnection && close). Good. > However, it doesn't (yet) solve the real problem: if I disconnect the > scanner while the device file is openend and then write to the scanner > the kernel crashes. Where does it die? What's the oops output? thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
