From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH 2/3] block: do not check bdrv_file_open
Date: Thu, 19 Jan 2023 14:17:37 +0100 [thread overview]
Message-ID: <Y8lC8d0/XdEct7Mc@redhat.com> (raw)
In-Reply-To: <20221212131700.250209-3-pbonzini@redhat.com>
Am 12.12.2022 um 14:16 hat Paolo Bonzini geschrieben:
> The set of BlockDrivers that have .bdrv_file_open coincides with those
> that have .protocol_name and guess what---checking drv->bdrv_file_open
> is done to see if the driver is a protocol. So check drv->protocol_name
> instead.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> block.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/block.c b/block.c
> index 0a625a489a6e..7a66cc2ea23a 100644
> --- a/block.c
> +++ b/block.c
> @@ -911,7 +911,6 @@ BlockDriver *bdrv_find_protocol(const char *filename,
> int i;
>
> GLOBAL_STATE_CODE();
> - /* TODO Drivers without bdrv_file_open must be specified explicitly */
>
> /*
> * XXX(hch): we really should not let host device detection
> @@ -1618,7 +1617,7 @@ static int bdrv_open_driver(BlockDriverState *bs, BlockDriver *drv,
> bs->opaque = g_malloc0(drv->instance_size);
>
> assert(!drv->bdrv_needs_filename || bs->filename[0]);
> - if (drv->bdrv_file_open) {
> + if (drv->bdrv_open) {
> ret = drv->bdrv_file_open(bs, options, open_flags, &local_err);
> } else if (drv->bdrv_open) {
> ret = drv->bdrv_open(bs, options, open_flags, &local_err);
I suppose you mean drv->protocol_name for the first if condition?
The bug will disappear again after patch 3, but this intermediate state
is very broken.
Kevin
next prev parent reply other threads:[~2023-01-19 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 13:16 [PATCH 0/3] block: remove separate bdrv_file_open callback Paolo Bonzini
2022-12-12 13:16 ` [PATCH 1/3] block: apply assertion more widely Paolo Bonzini
2022-12-12 13:16 ` [PATCH 2/3] block: do not check bdrv_file_open Paolo Bonzini
2023-01-19 13:17 ` Kevin Wolf [this message]
2023-04-21 9:35 ` Paolo Bonzini
2022-12-12 13:17 ` [PATCH 3/3] block: remove separate bdrv_file_open callback Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2023-03-09 8:50 [PATCH 0/3] " Paolo Bonzini
2023-03-09 8:50 ` [PATCH 2/3] block: do not check bdrv_file_open Paolo Bonzini
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=Y8lC8d0/XdEct7Mc@redhat.com \
--to=kwolf@redhat.com \
--cc=pbonzini@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).