• E
    nbd: Implement NBD_OPT_GO on server · f37708f6
    Eric Blake 提交于
    NBD_OPT_EXPORT_NAME is lousy: per the NBD protocol, any failure
    requires us to close the connection rather than report an error.
    Therefore, upstream NBD recently added NBD_OPT_GO as the improved
    version of the option that does what we want [1], along with
    NBD_OPT_INFO that returns the same information but does not
    transition to transmission phase.
    
    [1] https://github.com/NetworkBlockDevice/nbd/blob/extension-info/doc/proto.md
    
    This is a first cut at the information types, and only passes the
    same information already available through NBD_OPT_LIST and
    NBD_OPT_EXPORT_NAME; items like NBD_INFO_BLOCK_SIZE (and thus any
    use of NBD_REP_ERR_BLOCK_SIZE_REQD) are intentionally left for
    later patches.
    Signed-off-by: NEric Blake <eblake@redhat.com>
    Message-Id: <20170707203049.534-7-eblake@redhat.com>
    Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
    f37708f6
trace-events 4.9 KB