Re: [linux-usb-devel] [2.6.22-rc7] khubd NULL deref oops...

2007-07-12 Thread Cornelia Huck
On Wed, 11 Jul 2007 17:41:13 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote: > On Wed, 11 Jul 2007, Daniel J Blueman wrote: > > > > Try disabling CONFIG_USB_SUSPEND. It makes lots of USB bugs go away > > > > I'll give it a shot. For the record, I wasn't trying to perform a > > suspend at thi

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-17 Thread Cornelia Huck
On Mon, 16 Apr 2007 15:12:47 -0700, Greg KH <[EMAIL PROTECTED]> wrote: > Ah, just found this original thread, now Cornelia's patches make more > sense... I would have included a pointer, but couldn't access marc yesterday evening, sorry... > > On Fri, Apr 13, 2007 at 11:24:58AM -0400, Alan Ster

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-16 Thread Cornelia Huck
On Mon, 16 Apr 2007 10:43:01 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote: > Actually it has to be done in kobject_init() since the release method can > be called any time after that, even if the kobject is never add'ed. True. This would also imply that we only ever must free a kobject with

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-16 Thread Cornelia Huck
On Fri, 13 Apr 2007 11:24:58 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote: > I have to admit, this is a puzzler. I'm beginning to think there should > be two types of module references: Those which (like module dependency) > will prevent rmmod from running, and those which (like the one he

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Cornelia Huck
On Fri, 13 Apr 2007 16:15:18 +0200, "Markus Rechberger" <[EMAIL PROTECTED]> wrote: > most dvb usb drivers call the device node unregistration when a device > gets unplugged (when > At this time the filehandle can still be open, the patch on that site > sets a flag that disallows > any further ac

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Cornelia Huck
On Fri, 13 Apr 2007 13:42:04 +0200, "Markus Rechberger" <[EMAIL PROTECTED]> wrote: > seems like you have the same problem as the dvb framework has/had. > > http://mcentral.de/hg/~mrec/v4l-dvb-stable > > The last 3 changesets do the trick to not oops, it will delay the > deinitialization of the

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Cornelia Huck
On Thu, 12 Apr 2007 17:23:18 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote: > Here's a not-so-theoretical question. > > I've got a module which registers a struct device. (It represents a > virtual device, not a real one, but that doesn't matter.) Obviously the > module's exit routine has t

Re: [linux-usb-devel] [GIT PATCH] USB fixes for 2.6.20-rc5

2007-01-23 Thread Cornelia Huck
t to re-parent the devices, they should work, > > right? > > Actually even that was broken for me. If removing the device_is_registered() check helps you, I'd lobby for the inclusion of that part (and leave device_move(dev, NULL) for post-2.6.20). (It should help for devices with

Re: [linux-usb-devel] [PATCH] driver core: handle bus_attach_device() failure

2006-10-09 Thread Cornelia Huck
; put_device(dev); > return error; > + BusAttachError: > + bus_remove_device(dev); > BusError: > device_pm_remove(dev); > PMError: This won't quite work :) See also http://marc.theaimsgroup.com/?l=linux-kernel&m=116008235424179&w=2 ff. for a disc