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)?
-- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
