Hi Hannes, I was going through one of the slide posted at below link.
http://events.linuxfoundation.org/sites/events/files/slides/SCSI-EH.pdf Slide #59 has below data. I was trying to correlate with latest upstream code, but do not understand few things. Does Linux handle blocking I/O to the device and target before it actually start legacy EH recovery ? Also, how does linux scsi stack achieve task set abort ? Proposed SCSI EH strategy • Send command aborts after timeout • EH Recovery starts: ‒ Block I/O to the device ‒ Issue 'Task Set Abort' ‒ Block I/O to the target ‒ Issue I_T Nexus Reset ‒ Complete outstanding command on success ‒ Engage current EH strategy ‒ LUN Reset, Target Reset etc Thanks, Kashyap -- 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
