From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] blockdev: enable non-root nodes for transaction drive-backup source
Date: Tue, 18 Jun 2019 10:24:05 -0400 [thread overview]
Message-ID: <a4aef1ae-d53e-7bfd-efc1-4a1ce9a40254@redhat.com> (raw)
In-Reply-To: <20190618140804.59214-1-vsementsov@virtuozzo.com>
On 6/18/19 10:08 AM, Vladimir Sementsov-Ogievskiy wrote:
> We forget to enable it for transaction .prepare, while it is already
> enabled in do_drive_backup since commit a2d665c1bc362
> "blockdev: loosen restrictions on drive-backup source node"
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
>
> Hmm, I've to add John by hand, get_maintainer.pl don't report him.
> Shouldn't we include blockdev.c into Block Jobs in MAINTAINERS?
> It definitely related to block jobs.
>
> blockdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/blockdev.c b/blockdev.c
> index b5c0fd3c49..4ae81d687a 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -1775,7 +1775,7 @@ static void drive_backup_prepare(BlkActionState *common, Error **errp)
> assert(common->action->type == TRANSACTION_ACTION_KIND_DRIVE_BACKUP);
> backup = common->action->u.drive_backup.data;
>
> - bs = qmp_get_root_bs(backup->device, errp);
> + bs = bdrv_lookup_bs(backup->device, backup->device, errp);
> if (!bs) {
> return;
> }
>
Ah, tch. I should extend 256 too in this case. Would you like me to take
care of that?
Jokingly: "drive-backup is a legacy interface, please don't use it!"
--js
next prev parent reply other threads:[~2019-06-18 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 14:08 [Qemu-devel] [PATCH] blockdev: enable non-root nodes for transaction drive-backup source Vladimir Sementsov-Ogievskiy
2019-06-18 14:24 ` John Snow [this message]
2019-06-18 14:32 ` Vladimir Sementsov-Ogievskiy
2019-06-18 14:57 ` John Snow
2019-06-19 19:12 ` Max Reitz
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=a4aef1ae-d53e-7bfd-efc1-4a1ce9a40254@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).