From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "dab21774@gmail.com" <dab21774@gmail.com>
Cc: "hch@lst.de" <hch@lst.de>, "ddiss@suse.de" <ddiss@suse.de>,
"hare@suse.com" <hare@suse.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"agrover@redhat.com" <agrover@redhat.com>,
"nab@linux-iscsi.org" <nab@linux-iscsi.org>,
"stable@vger.kernel.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 [thread overview]
Message-ID: <1496704650.2623.34.camel@sandisk.com> (raw)
In-Reply-To: <CALiN7rzL7YEH0rttFCURoTEkDNwqnC5zHO+Zr=MhjE8R+q-DEA@mail.gmail.com>
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.
next prev parent reply other threads:[~2017-06-05 23:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170523234854.21452-1-bart.vanassche@sandisk.com>
2017-05-23 23:48 ` [PATCH 04/33] target: Fix BYTCHK=0 handling for VERIFY and WRITE AND VERIFY commands Bart Van Assche
2017-06-02 4:15 ` Nicholas A. Bellinger
2017-06-02 16:52 ` Bart Van Assche
2017-06-03 5:32 ` Nicholas A. Bellinger
2017-06-03 5:37 ` Nicholas A. Bellinger
2017-06-05 16:49 ` Bart Van Assche
2017-06-05 22:32 ` David Butterfield
2017-06-05 23:17 ` Bart Van Assche [this message]
2017-05-23 23:48 ` [PATCH 08/33] target: Fix a deadlock between the XCOPY code and iSCSI session shutdown Bart Van Assche
2017-06-02 4:35 ` Nicholas A. Bellinger
2017-05-23 23:48 ` [PATCH 09/33] configfs: Introduce config_item_get_unless_zero() Bart Van Assche
2017-05-28 9:33 ` Christoph Hellwig
2017-05-28 16:37 ` Bart Van Assche
2017-06-13 23:22 ` Mike Christie
2017-05-23 23:48 ` [PATCH 15/33] xen/scsiback: Fix a use-after-free Bart Van Assche
2017-05-23 23:48 ` [PATCH 16/33] xen/scsiback: Replace a waitqueue and a counter by a completion Bart Van Assche
2017-05-23 23:48 ` [PATCH 17/33] xen/scsiback: Make TMF processing slightly faster Bart Van Assche
2017-05-23 23:48 ` [PATCH 25/33] target/iscsi: Avoid overflowing the receive buffer Bart Van Assche
2017-05-23 23:48 ` [PATCH 29/33] target/iscsi: Simplify timer manipulation code Bart Van Assche
[not found] ` <20170523234854.21452-16-bart.vanassche@sandisk.com>
2017-05-26 9:57 ` [PATCH 15/33] xen/scsiback: Fix a use-after-free Juergen Gross
2017-06-03 5:40 ` Nicholas A. Bellinger
[not found] ` <1496468455.27407.305.camel@haakon3.risingtidesystems.com>
2017-06-03 7:04 ` Nicholas A. Bellinger
[not found] ` <1496473471.27407.317.camel@haakon3.risingtidesystems.com>
2017-06-03 7:06 ` Juergen Gross
[not found] ` <20170523234854.21452-17-bart.vanassche@sandisk.com>
2017-05-26 10:13 ` [PATCH 16/33] xen/scsiback: Replace a waitqueue and a counter by a completion Juergen Gross
2017-06-03 5:41 ` Nicholas A. Bellinger
[not found] ` <20170523234854.21452-18-bart.vanassche@sandisk.com>
2017-05-26 10:18 ` [PATCH 17/33] xen/scsiback: Make TMF processing slightly faster Juergen Gross
2017-06-03 5:41 ` Nicholas A. Bellinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1496704650.2623.34.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=agrover@redhat.com \
--cc=dab21774@gmail.com \
--cc=ddiss@suse.de \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=nab@linux-iscsi.org \
--cc=stable@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.