I've been chasing a BUG_ON in blk_requeue_request which seems to occur in scenarios where we are seeing lots of SCSI aborts. As I've been digging through the completion paths and abort paths, I've noticed if the following sequence occurs, we are likely to hit this issue: 1. scsi_cmd times out, async abort issued 2. LLDD aborts command, LLDD calls scsi_done for the aborted command from interrupt handler when aborted command comes back 3. If result of the aborted command is something like DID_ERROR and we allow retries, then in scsi_done processing, we'll call scsi_queue_insert which then calls blk_requeue_request 4. Returning from the LLDD's eh_abort handler, scsi_error sees the abort was successful, and then calls scsi_queue_insert for the aborted command, which also calls blk_requeue_request where we hit the BUG_ON because the command has been queued again. This is occurring for the non blk_rq_tagged case, for reference, so blk_requeue_request doesn't call blk_queue_end_tag which might cause this to not be hit... Should a LLDD NOT call scsi_done for commands it aborts? We've seen the issue above on both ibmvfc and mpt2sas, but I know there are other LLDDs that call scsi_done in this case, but just do it before eh_abort returns. Or is it expected the LLDD will only ever return DID_ABORT on the aborted command, which looks like it might prevent this issue as well, however, that seems racy and then we'd also need to add some memory barriers around the checking / setting of scmd->eh_eflags I would think. Or am I missing something and headed down the wrong path? Thanks, Brian -- Brian King Power Linux I/O IBM Linux Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
