On Sun, Aug 24, 2014 at 10:46:57AM +0200, Hans de Goede wrote: > To be clear I believe there may be a bug or 2 in the uas.c abort code > paths, not in the scsi core or sd drivers. > > But getting more eyes on these definitely makes sense. Should I CC > linux-scsi@vger on issues like this, or should I get the users > to file a bug at bugzilla.kernel.org (my own preference would be to > do the latter, as that keeps all info in a single place).
Please Cc linux-scsi. I and some others definitively don't have the pain and patience to deal with bugzilla. > uas is only enabled in 3.15 and newer so that patch should be present. There have been a few more important fixes since 3.15: ac61d19559349e205dad7b5122b281419aa74a82 scsi: set correct completion code in scsi_send_eh_cmnd() 8922a908908ff947f1f211e07e2e97f1169ad3cb scsi_error: fix invalid setting of host byte a33c070bced8b283e22e8dbae35177a033b810bf scsi_error: set DID_TIME_OUT correctly make sure you have those as well. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
