The patch titled usb-storage: wait for URB to complete has been added to the -mm tree. Its filename is usb-storage-wait-for-urb-to-complete.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: usb-storage: wait for URB to complete From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> We all failed to notice that Franck's recent update to usb-storage allowed an URB to complete after its context data was no longer valid. This patch (as746) makes the driver wait for the URB to complete whenever there's a timeout. Although timeouts in usb-storage are relatively uncommon, they do occur. Without this patch the code in 2.6.18-rc1 will fault within an interrupt handler, which is not nice at all. Signed-off-by: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> Cc: Greg KH <greg@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- drivers/usb/storage/transport.c | 2 +- 1 files changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/usb/storage/transport.c~usb-storage-wait-for-urb-to-complete drivers/usb/storage/transport.c --- a/drivers/usb/storage/transport.c~usb-storage-wait-for-urb-to-complete +++ a/drivers/usb/storage/transport.c @@ -180,7 +180,7 @@ static int usb_stor_msg_common(struct us if (timeleft <= 0) { US_DEBUGP("%s -- cancelling URB\n", timeleft == 0 ? "Timeout" : "Signal"); - usb_unlink_urb(us->current_urb); + usb_kill_urb(us->current_urb); } /* return the URB status */ _ Patches currently in -mm which might be from stern@xxxxxxxxxxxxxxxxxxx are e100-disable-interrupts-at-boot.patch usb-storage-wait-for-urb-to-complete.patch block-layer-early-detection-of-medium-not-present.patch scsi-core-and-sd-early-detection-of-medium-not-present.patch sd-early-detection-of-medium-not-present.patch task-watchers-task-watchers.patch task-watchers-add-support-for-per-task-watchers.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html