On 04/28/13 18:19, ronnie sahlberg wrote:
Hi List,
Interested in SCSI tests?
I have a reasonable SCSI (mainly SBC) testsuite at
https://github.com/sahlberg/libiscsi
while I am mainly interested in testing of iSCSI targets, most of my
tests so far are for the SCSI protocol
so they work quite well on devices connected to any kind of transport,
as long as you re-export them via iSCSI.
(For example using a simple passthrough device with TGT.)
At some stage I will redo some of the framework so that it can
optionally talk directly to a /dev/sg* device, but reexporting via TGT
works well enough for now.
Hello Ronnie,
Thanks for making this software publicly available. I have a question
about one particular test though. In the output of the test suite I
found the following: <quote>Test READ16 with non-zero RDPROTECT. Device
does not support/use protection information. All commands should
fail.</quote>
However, in SBC-3 I found the following: <quote>If type 0 protection is
enabled and the RDPROTECT field, the WRPROTECT field, the VRPROTECT
field, or the ORPROTECT field is set to a non-zero value, then medium
access commands are invalid and may be terminated by the device server
with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the additional sense code set to INVALID FIELD IN CDB.</quote>
Apparently your test suite considers not failing READ16 with non-zero
RDPROTECT field as an error. However, if I interpret the above paragraph
from SBC-3 correctly that behavior seems compliant to me ?
Bart.
--
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
