From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42765) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bD65G-0003RQ-Ge for qemu-devel@nongnu.org; Wed, 15 Jun 2016 04:21:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bD65C-0007G7-AU for qemu-devel@nongnu.org; Wed, 15 Jun 2016 04:21:57 -0400 Date: Wed, 15 Jun 2016 10:03:46 +0200 From: Wouter Verhelst Message-ID: <20160615080346.GA6994@grep.be> References: <1463006384-7734-1-git-send-email-eblake@redhat.com> <1463006384-7734-5-git-send-email-eblake@redhat.com> <852e526a-5235-499a-741e-a695f5e74f83@redhat.com> <575EA656.80508@redhat.com> <6DD06745-C91C-4BFB-BFE5-92E5982ACB42@alex.org.uk> <11f620d2-a51d-5235-5abd-4ced314c9090@redhat.com> <38ABE56B-CA23-4372-A413-CDA72BDAE86A@alex.org.uk> <20160615070522.GC3787@grep.be> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <20160615070522.GC3787@grep.be> Subject: Re: [Qemu-devel] [Nbd] [PATCH v4 04/11] nbd: Improve server handling of bogus commands List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Bligh Cc: "nbd-general@lists.sourceforge.net" , Paolo Bonzini , "qemu-devel@nongnu.org" , qemu block --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 15, 2016 at 09:05:22AM +0200, Wouter Verhelst wrote: > There are more clients than the Linux and qemu ones, but I think it's > fair to say that those two are the most important ones. If they agree > that a read reply which errors should come without payload, then I think > we should update the standard to say that, too. I've just pushed a commit that changes the spec (and the implementation) so that if a server encounters a read error, it does not send a payload. In other words, the current behaviour of qemu is correct, is now documented to be correct, and should not be changed. Regards, --=20 < ron> I mean, the main *practical* problem with C++, is there's like a doz= en people in the world who think they really understand all of its rule= s, and pretty much all of them are just lying to themselves too. -- #debian-devel, OFTC, 2016-02-12 --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXYQvdAAoJEMKUD5Ub3wqdFkIP/0Cz0BwLckBzuI9FAd5k6lXy P3dSQ7LWa5GeOyjw0e4Z8iZKrUligWgWBMe+aui1Yz14vB7i/0vMLVpoRFyCpXwb P1nZsNsEhDeLXOj611YP5ja6mk9M7bgLGWr/+Eesu4ZBCS2cQJtzO/5nBpp1u3fA L7XHkAEVZFO9HHDgG1729Kls1AuNL/XwFqDQ29x0S2vyfS3Hl6Gua0uZlwjyzRz3 xautc3i3Gn2sxt4VdR6G0oZH8sf4LHNNtpj/xS++VJ1Q5CypvWiebNIgnch8M47c T3VXn1uXepoiQA169TC/CFqwIepzJS4P+WuLXLkZz7lnReLFAXS5nG0FEIPSZphO RQ3FDvl15Bpwem0L8z9FkvDTRWOFKrI4J9x0YUjrCC55/hE9TP3Mpnh56bYt0gFc TVrFe26T49JSB6beX0EOf3fMYLMQ6HZeob/+t3K9QhM3X/KfpbaMIOpjVfNdUbi6 PYqDaxinCpATyl4/KKFBMBEQqeJ5ML/L/Em+fy73Ih8SgOh5evmY0KxTFO7LGN69 rj4oud1D9cXTKl5HgvDaZqBqe69KcLB0c/LaTnjAauuI5GP0cvvJF0heTyb77EOF +Muj5qPDDWaKjGeXKMnOND1RcafAMpl2XatmdTFN1RGUl/ch9gaDfZcQeUJMxfWd HMgbMfcrZoNq+4/fYn63 =UvEP -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c--