From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43617) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aliLL-0002Mq-KV for qemu-devel@nongnu.org; Thu, 31 Mar 2016 15:33:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aliLH-0006gL-Kb for qemu-devel@nongnu.org; Thu, 31 Mar 2016 15:33:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36054) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aliLH-0006gE-Fb for qemu-devel@nongnu.org; Thu, 31 Mar 2016 15:33:19 -0400 From: Eric Blake Message-ID: <56FD7B7E.4060004@redhat.com> Date: Thu, 31 Mar 2016 13:33:18 -0600 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bV1tR4eME0TLNACiB48apn1fMNeSn0bMd" Subject: [Qemu-devel] Is NBD_CMD_FLAG_FUA valid during NBD_CMD_FLUSH? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" , "nbd-general@lists.sourceforge.net" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bV1tR4eME0TLNACiB48apn1fMNeSn0bMd Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Qemu's nbd-client is setting NBD_CMD_FLAG_FUA during a flush command, but the official NBD protocol documentation doesn't describe this as valid (it merely states that flush must not have a reply until all acknowledged writes have hit permanent storage). Does this flag make sense (what semantics would the flag add, and we need to fix the NBD docs as well as relax the reference implementation to allow the flag), or is it a bug in qemu (and the recent tightening of NBD to throw EINVAL on unsupported flags will trip up qemu)? --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --bV1tR4eME0TLNACiB48apn1fMNeSn0bMd 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/Xt+AAoJEKeha0olJ0NqGt4H/RJHnUeSTi08HvsgdBS7gvN1 0IAmL1W+UikGgiTSd9rsGW6KlilYsRA6yet3h3/QPEZGCDw0soA3PXuLUUZ863TU G0VNT+8oC+keyU+QJATZMJ/ceZK7zwnhm7ugZoCHTCZY8XfypPKg6emHMgEGGq2p AIRUo5+Ht1EEY+SplzoDArnKB4AtOVY3VtcW+dn2uoxTeSERy1xlIA+vP8qtQIox 4zrWm1oQGHM6hUgi3ZvrKvQlF7O0ikDtIlLVmYDuC6npp+rkEEga9F2l/yPve2U2 mpg9O0Sa8R6TGkl6YplM7dgNVgEssbxjbxKmwLgJwavZpPI1dCYg63fNlZ1mMHA= =rfbJ -----END PGP SIGNATURE----- --bV1tR4eME0TLNACiB48apn1fMNeSn0bMd--