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
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
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
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
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().