qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fabiano Rosas <farosas@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/5] block: Ensure non-protocol drivers can only be selected explicitly
Date: Tue, 20 Mar 2018 11:48:20 +0100	[thread overview]
Message-ID: <20180320104820.GB4865@localhost.localdomain> (raw)
In-Reply-To: <20180312220753.20096-1-farosas@linux.vnet.ibm.com>

Am 12.03.2018 um 23:07 hat Fabiano Rosas geschrieben:
> Block drivers can be selected by either protocol syntax:
> 
>   <protocol>:<filename>[:options]
> 
> or explicitly:
> 
>   driver=<driver>[,option=<opt1>...]
> 
> For the protocol syntax to work, drivers should set the protocol_name
> field of the BlockDriver structure and provide bdrv_file_open and
> bdrv_parse_filename implementations.
> 
> Conversely, block drivers that do not support the protocol syntax
> should instead implement bdrv_open and not have a protocol_name field.
> 
> Some drivers do not currently adhere to this and errors arise when
> trying to select them using the protocol syntax. For instance:
> 
>   $ qemu-img info replication:foo
>   qemu-img: block.c:2401: bdrv_open_inherit: \
>   Assertion `!!(flags & BDRV_O_PROTOCOL) == !!drv->bdrv_file_open' failed.
>   Aborted (core dumped)
> 
> This patch-set ensures that the following drivers are meeting the
> above criteria:
> - blkreplay
> - quorum
> - replication
> - throttle
> 
> Aside from that, documentation was added to make the above more
> explicit.

Thanks, applied to the block branch.

Kevin

      parent reply	other threads:[~2018-03-20 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 22:07 [Qemu-devel] [PATCH v2 0/5] block: Ensure non-protocol drivers can only be selected explicitly Fabiano Rosas
2018-03-12 22:07 ` [Qemu-devel] [PATCH v2 1/5] block/replication: Remove protocol_name field Fabiano Rosas
2018-03-12 22:07 ` [Qemu-devel] [PATCH v2 2/5] block/quorum: Remove protocol-related fields Fabiano Rosas
2018-03-14 15:15   ` Alberto Garcia
2018-03-12 22:07 ` [Qemu-devel] [PATCH v2 3/5] block/throttle: " Fabiano Rosas
2018-03-14 15:18   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-03-12 22:07 ` [Qemu-devel] [PATCH v2 4/5] block/blkreplay: " Fabiano Rosas
2018-03-12 22:07 ` [Qemu-devel] [PATCH v2 5/5] include/block/block_int: Document protocol related functions Fabiano Rosas
2018-03-20 10:48 ` Kevin Wolf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180320104820.GB4865@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=farosas@linux.vnet.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).