qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Manos Pitsidianakis <el13635@mail.ntua.gr>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com,
	mreitz@redhat.com, nsoffer@redhat.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH for-2.10] block: Skip implicit nodes in query-block/blockstats
Date: Wed, 19 Jul 2017 11:41:42 +0200	[thread overview]
Message-ID: <20170719094142.GC4617@noname.redhat.com> (raw)
In-Reply-To: <20170719092102.dg6g3qxg6zbmijq4@postretch>

[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]

[ Cc: qemu-stable ]

Am 19.07.2017 um 11:21 hat Manos Pitsidianakis geschrieben:
> On Wed, Jul 19, 2017 at 10:44:47AM +0200, Kevin Wolf wrote:
> >Commits 0db832f and 6cdbceb introduced the automatic insertion of filter
> >nodes above the top layer of mirror and commit block jobs. The
> >assumption made there was that since libvirt doesn't do node-level
> >management of the block layer yet, it shouldn't be affected by added
> >nodes.
> >
> >This is true as far as commands issued by libvirt are concerned. It only
> >uses BlockBackend names to address nodes, so any operations it performs
> >still operate on the root of the tree as intended.
> >
> >However, the assumption breaks down when you consider query commands,
> >which return data for the wrong node now. These commands also return
> >information on some child nodes (bs->file and/or bs->backing), which
> >libvirt does make use of, and which refer to the wrong nodes, too.
> >
> >One of the consequences is that oVirt gets wrong information about the
> >image size and stops the VM in response as long as a mirror or commit
> >job is running:
> >
> >https://bugzilla.redhat.com/show_bug.cgi?id=1470634
> >
> >This patch fixes the problem by hiding the implict nodes created
> s/implict/implicit

Fixed.

> Also, it seems like qemu-stable wasn't successfully CC'd (the patch
> is not in the list archives either).

Ah yes, forgot to actually CC it on the mail. Adding it to this mail.

> Reviewed-by: Manos Pitsidianakis <el13635@mail.ntua.gr>

Thanks!

Kevin

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2017-07-19  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19  8:44 [Qemu-devel] [PATCH for-2.10] block: Skip implicit nodes in query-block/blockstats Kevin Wolf
2017-07-19  9:21 ` [Qemu-devel] [Qemu-block] " Manos Pitsidianakis
2017-07-19  9:41   ` Kevin Wolf [this message]
2017-07-19 11:15 ` [Qemu-devel] " Peter Krempa
2017-07-19 12:09   ` Kevin Wolf
2017-07-19 12:45 ` Eric Blake
2017-07-19 13:05 ` Markus Armbruster
2017-07-19 13:19   ` Nir Soffer
2017-07-19 13:45   ` Kevin Wolf

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=20170719094142.GC4617@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=el13635@mail.ntua.gr \
    --cc=mreitz@redhat.com \
    --cc=nsoffer@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).