From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55130) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1al357-00080X-Rm for qemu-devel@nongnu.org; Tue, 29 Mar 2016 19:29:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1al354-0004vW-DZ for qemu-devel@nongnu.org; Tue, 29 Mar 2016 19:29:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36991) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1al354-0004vQ-8Q for qemu-devel@nongnu.org; Tue, 29 Mar 2016 19:29:50 -0400 References: <1459173555-4890-1-git-send-email-eblake@redhat.com> <1459292460-6875-1-git-send-email-eblake@redhat.com> <1459292460-6875-4-git-send-email-eblake@redhat.com> From: Eric Blake Message-ID: <56FB0FEC.5070305@redhat.com> Date: Tue, 29 Mar 2016 17:29:48 -0600 MIME-Version: 1.0 In-Reply-To: <1459292460-6875-4-git-send-email-eblake@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2tv9RiarNqERuFMNjKTd16SW8vuwee1W2" Subject: Re: [Qemu-devel] [PATCH v2 3/3] doc: Propose Structured Read extension List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: nbd-general@lists.sourceforge.net Cc: w@uter.be, qemu-devel@nongnu.org, alex@alex.org.uk This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2tv9RiarNqERuFMNjKTd16SW8vuwee1W2 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 03/29/2016 05:01 PM, Eric Blake wrote: > The existing transmission phase protocol is difficult to sniff, > because correct interpretation of the server stream requires > context from the client stream (or risks false positives if > data payloads happen to contain the protocol magic numbers). It > also prohibits the ability to do efficient sparse reads, or to > return a short read where an error is reported without also > sending length bytes of (bogus) data. >=20 > +* `NBD_CMD_READ` > + > + If `NBD_OPT_STRUCTURED_READ` was not negotiated, then a read > + request MUST always be answered by a single non-structured > + response, as documented above (using magic 0x67446698 > + `NBD_REPLY_MAGIC`, and containing length bytes of data according > + to the client's request, although those bytes MAY be invalid if an= > + error is returned, and the connection MUST if an error occurs MUST be closed (I hate it when I send patches before 'git commit --amend' on the final unsaved changes in my editor...) > + after a header claiming no error). > + --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --2tv9RiarNqERuFMNjKTd16SW8vuwee1W2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW+w/sAAoJEKeha0olJ0NqrS4IAJVyfk4etih8WR+FVVgCgyBX zmu+85r+sCvU0tqaIdYtrzlaNLNZiT9PmXz5n8t2L+m5FaTlN9B0HDA5pybUG31z GqN1HvspEOVJR8zDV8lG8+pjx422bxc781mve8Zipu42CjRSGolAOLGHND+vzXXw We5KYoaf/qsi1DN0UWzb50GzQr+u2GA8J9ciEf3AesMf6w8XfcgMgFfMNFfRpMxV 1oMFfswLy7kBVzlg2x58f4eeJSVOKctDMPQZP0pieABPObaVdnNrjAJgeaU7rBvd du992JgNmiCWDvuNmOFnVG+Yso5GmsEtBD6MoA09ZNMx2YWs1lK4N55cqKX08bs= =28I0 -----END PGP SIGNATURE----- --2tv9RiarNqERuFMNjKTd16SW8vuwee1W2--