As discussed on the call, TMF may fail if it can't abort the command for some reason, so insert the word "successfully". I will apply this once the minutes are published. Thanks, Rusty. diff --git a/content.tex b/content.tex index 56f58fa..9e71098 100644 --- a/content.tex +++ b/content.tex @@ -4811,7 +4811,7 @@ struct virtio_scsi_ctrl_tmf
Similarly, the device MUST complete the selected commands (possibly
with a VIRTIO_SCSI_S_ABORTED response code) upon receiving an "abort
task" or "abort task set" TMF. Such effects MUST take place before - the TMF itself is completed, and the device MUST use memory barriers + the TMF itself is successfully completed, and the device MUST use memory barriers
appropriately in order to ensure that the driver sees these writes
in the correct order.
