Re: [PATCH] usb hub: send clear_tt_buffer_complete events when canceling TT clear work

2012-10-01 Thread Octavian Purdila
Hi Alan, On Mon, Oct 1, 2012 at 8:48 PM, Alan Stern wrote: > > On Mon, 1 Oct 2012, Alan Stern wrote: > > > On Mon, 1 Oct 2012, Octavian Purdila wrote: > > > > > There is a race condition in the USB hub code with regard to handling > > > TT clear requests that can get the HCD driver in a deadlock.

Re: [PATCH] usb hub: send clear_tt_buffer_complete events when canceling TT clear work

2012-10-01 Thread Alan Stern
On Mon, 1 Oct 2012, Alan Stern wrote: > On Mon, 1 Oct 2012, Octavian Purdila wrote: > > > There is a race condition in the USB hub code with regard to handling > > TT clear requests that can get the HCD driver in a deadlock. Usually > > when an TT clear request is scheduled it will be executed im

Re: [PATCH] usb hub: send clear_tt_buffer_complete events when canceling TT clear work

2012-10-01 Thread Alan Stern
On Mon, 1 Oct 2012, Octavian Purdila wrote: > There is a race condition in the USB hub code with regard to handling > TT clear requests that can get the HCD driver in a deadlock. Usually > when an TT clear request is scheduled it will be executed immediately: > However, if a suspend operation is

[PATCH] usb hub: send clear_tt_buffer_complete events when canceling TT clear work

2012-10-01 Thread Octavian Purdila
There is a race condition in the USB hub code with regard to handling TT clear requests that can get the HCD driver in a deadlock. Usually when an TT clear request is scheduled it will be executed immediately: <7>[6.077583] usb 2-1.3: unlink qh1-0e01/f4d4db00 start 0 [1/2 us] <3>[6.078041]