On Mon, 2017-06-05 at 16:32 -0600, David Butterfield wrote: > Since the spec provides the BYTCHK field for WRITE VERIFY and refers to its > definition in VERIFY, I take that to mean the intention is that BYTCHK=00 be > treated as with VERIFY; in other words, the VERIFY step ignores TRANSFER > LENGTH (even though the WRITE step uses it), and the VERIFY step checks > the protection information based on the VRPROTECT field in the CDB > (WRPROTECT in the WRITE CDB), as described in the VERIFY section. > > I think the spec is broken here, and this is my plausible > interpretation of the intent. Hello Dave, That's a good point. As far as I know only AIX submits the WRITE AND VERIFY command. So it would be useful to know what value AIX sets the BYTCHK field to. Bart.-- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
