From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from esa3.hgst.iphmx.com ([216.71.153.141]:53234 "EHLO esa3.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751195AbdFEXRf (ORCPT ); Mon, 5 Jun 2017 19:17:35 -0400 From: Bart Van Assche To: "dab21774@gmail.com" CC: "hch@lst.de" , "ddiss@suse.de" , "hare@suse.com" , "target-devel@vger.kernel.org" , "agrover@redhat.com" , "nab@linux-iscsi.org" , "stable@vger.kernel.org" Subject: Re: [PATCH 04/33] target: Fix BYTCHK=0 handling for VERIFY and WRITE AND VERIFY commands Date: Mon, 5 Jun 2017 23:17:32 +0000 Message-ID: <1496704650.2623.34.camel@sandisk.com> References: <20170523234854.21452-1-bart.vanassche@sandisk.com> <20170523234854.21452-5-bart.vanassche@sandisk.com> <1496376930.27407.234.camel@haakon3.risingtidesystems.com> <1496422372.1214.9.camel@sandisk.com> <1496467944.27407.299.camel@haakon3.risingtidesystems.com> <1496681389.2623.11.camel@sandisk.com> In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: stable-owner@vger.kernel.org List-ID: 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 i= ts > definition in VERIFY, I take that to mean the intention is that BYTCHK=3D= 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. >=20 > 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.=