Re: [PATCH] drivers/usb: Delete XHCI command timer if necessary

2015-08-06 Thread Gavin Shan
On Thu, Aug 06, 2015 at 10:37:11AM +0300, Mathias Nyman wrote: On 06.08.2015 02:29, Greg KH wrote: On Thu, Aug 06, 2015 at 09:13:12AM +1000, Gavin Shan wrote: On Mon, Jul 27, 2015 at 12:08:05PM +1000, Gavin Shan wrote: When xhci_mem_cleanup() is called, it's possible that the command timer

Re: [PATCH] drivers/usb: Delete XHCI command timer if necessary

2015-08-06 Thread Mathias Nyman
On 06.08.2015 02:29, Greg KH wrote: On Thu, Aug 06, 2015 at 09:13:12AM +1000, Gavin Shan wrote: On Mon, Jul 27, 2015 at 12:08:05PM +1000, Gavin Shan wrote: When xhci_mem_cleanup() is called, it's possible that the command timer isn't initialized and scheduled. For those cases, to delete the

Re: [PATCH] drivers/usb: Delete XHCI command timer if necessary

2015-08-05 Thread Gavin Shan
On Mon, Jul 27, 2015 at 12:08:05PM +1000, Gavin Shan wrote: When xhci_mem_cleanup() is called, it's possible that the command timer isn't initialized and scheduled. For those cases, to delete the command timer causes soft-lockup as below stack dump shows. The patch avoids deleting the command

Re: [PATCH] drivers/usb: Delete XHCI command timer if necessary

2015-08-05 Thread Greg KH
On Thu, Aug 06, 2015 at 09:13:12AM +1000, Gavin Shan wrote: On Mon, Jul 27, 2015 at 12:08:05PM +1000, Gavin Shan wrote: When xhci_mem_cleanup() is called, it's possible that the command timer isn't initialized and scheduled. For those cases, to delete the command timer causes soft-lockup as

[PATCH] drivers/usb: Delete XHCI command timer if necessary

2015-07-26 Thread Gavin Shan
When xhci_mem_cleanup() is called, it's possible that the command timer isn't initialized and scheduled. For those cases, to delete the command timer causes soft-lockup as below stack dump shows. The patch avoids deleting the command timer if it's not scheduled with the help of timer_pending().