summaryrefslogtreecommitdiffstats
path: root/drivers/mfd/wm8994-irq.c
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2020-01-17 10:47:13 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-01-17 17:57:04 +0100
commitfdd64df7b9d1e20dbe28c9c205682b66ad821e6c (patch)
tree68c314a1d2f3f1c9f1308ddc53f1fd4feb978bd9 /drivers/mfd/wm8994-irq.c
parent50f737ab96c7977317a47e60c52f4f0ce8b64e7f (diff)
downloadlinux-fdd64df7b9d1e20dbe28c9c205682b66ad821e6c.tar.gz
linux-fdd64df7b9d1e20dbe28c9c205682b66ad821e6c.tar.bz2
linux-fdd64df7b9d1e20dbe28c9c205682b66ad821e6c.zip
USB: usbfs: Always unlink URBs in reverse order
When the kernel unlinks a bunch of URBs for a single endpoint, it should always unlink them in reverse order. This eliminates any possibility that some URB x will be unlinked before it can execute but the following URB x+1 will execute before it can be unlinked. Such an event would be bad, for obvious reasons. Chris Dickens pointed out that usbfs doesn't behave this way when it is unbound from an interface. All pending URBs are cancelled, but in the order of submission. This patch changes the behavior to make the unlinks occur in reverse order. It similarly changes the behavior when usbfs cancels the continuation URBs for a BULK endpoint. Suggested-by: Chris Dickens <christopher.a.dickens@gmail.com> Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Link: https://lore.kernel.org/r/Pine.LNX.4.44L0.2001171045380.1571-100000@iolanthe.rowland.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/mfd/wm8994-irq.c')
0 files changed, 0 insertions, 0 deletions