On Thu, Jun 22, 2006 at 05:22:30PM -0700, Greg KH wrote:
> On Thu, Jun 22, 2006 at 05:17:32PM -0700, Andrew Morton wrote:
> > Jeremy Fitzhardinge <[email protected]> wrote:
> > >
> > > Greg KH wrote:
> > > > I saw this once when debugging the usb code, but could never reproduce
> > > > it, so I attributed it to an incomplete build at the time, as a reboot
> > > > fixed it.
> > > >
> > > > Is this easy to trigger for you?
> > > >
> > >
> > > This is the same oops as I posted yesterday: "2.6.17-mm1: oops in
> > > Bluetooth stuff, usbdev_open". I haven't seen it since...
> > >
> >
> > That's a kernel-wide list of USB devices, isn't it? Which means that some
> > driver other than the bluetooth one has got itself freed up while still
> > being on the list.
> >
> > If so, it could be any driver at all..
>
> Hopefully we have the list locked properly while we are walking it, so
> that should not happen, but I'll go back and verify that I got it all
> correct...
Oh crap, that's it. There's a race when a device switches
configurations and the endpoints disappear. I was locking in the wrong
functions... Let me beat on the fix for a bit to make sure I have it
right.
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
