[lkml]   [2004]   [May]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] hci-usb bugfix
Hi Oliver,

> > which results in the same as if we set NULL for the private pointer when
> > we claim the second interface. If this really happens then we have more
> > problems in the driver itself, because this case won't be handled in
> > either way. However I don't think that this will happen, because for
> You can trigger it in software through usbfs.

I've never done this before. Can you show me how?

> > Bluetooth devices interface 0 and 1 can be seen as a unit. The only
> > reason that this was split over two interfaces, was that you don't have
> > to stop the bulk transfers when you change the altsetting on the second
> > interface.
> Yes, but you should really stop using the second interface _before_
> returning returning from disconnect() for _that_ interface. You will
> operate correctly if the primary interface is disconnected first,
> but you cannot depend on that. If the secondary interface is
> disconnected first, you have a window where you illegally use an
> interface you no longer own.

You are absolutely right and this needs to be fixed, but this problem is
a different one than that my patch fixes. However this problem is now on
my todo list. Thanks for making me aware of.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [W:0.075 / U:14.336 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site