On 05/17/2016 10:39 AM, Richard W.M. Jones wrote: > On Tue, May 17, 2016 at 09:59:02AM -0600, Eric Blake wrote: >> On 05/17/2016 09:52 AM, Eric Blake wrote: >>>>> Perhaps nbdkit should implement NBD_OPT_LIST returning just "" (the >>>>> default name) as its only list entry? >>>> >>>> Or "default". >>> >>> As I read the protocol, I don't see "default" as a permissible name of >>> the default export, just "". >>> >>> Also, we currently state that NBD_OPT_LIST has zero or more >>> NBD_REP_SERVER replies, which means that it is valid for the command to >>> succeed with NBD_REP_ACK _without_ advertising any exports at all >>> (rather annoying in that it tells you nothing about whether >>> NBD_OPT_EXPORT_NAME/NBD_OPT_GO will succeed anyways). Should we reword >>> that to require that if NBD_REP_ACK is sent, then at least one >>> NBD_REP_SERVER reply was given (where "" is the obvious name, but at the >>> same time where "" is not mandatory if some other name is given)? >> >> Okay, I just downloaded nbdkit code and checked; nbdkit is sending 0 >> entries and NBD_REP_ACK (for success), and NOT an error code; so it is >> implying that there are NO known export names but that the command was >> recognized. > > Bleah you are right. I misread the code I wrote :-( > > We can add a empty string list entry there easily enough. Will adding the empty string break qemu 2.5 connections? qemu 2.6 is picky in that if the name it is requesting is not in the advertised list, it gives up; but if there is NO advertised list, it assumes the name will just work. Since nbdkit has the latter behavior, I'm thinking that nbdkit returning NBD_REP_ERR_UNSUP instead of NBD_REP_ACK is a smarter course of action. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature