All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, mreitz@redhat.com, eblake@redhat.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.11 0/2] Fix 'qemu-img info' on mirror target
Date: Mon, 20 Nov 2017 22:22:38 +0800	[thread overview]
Message-ID: <20171120142238.GA6828@lemon.lan> (raw)
In-Reply-To: <20171120141141.24626-1-kwolf@redhat.com>

On Mon, 11/20 15:11, Kevin Wolf wrote:
> There is no reason to forbid 'qemu-img info' for an image that is used
> as a mirror target (or intermediate image of a commit job) at the same
> time.
> 
> This fixes the problem reported on qemu-discuss:
> https://lists.gnu.org/archive/html/qemu-discuss/2017-11/msg00039.html
> 
> Kevin Wolf (2):
>   block: Don't use BLK_PERM_CONSISTENT_READ for format probing
>   block: Don't request I/O permission with BDRV_O_NO_IO
> 
>  block.c               |  5 ++++-
>  block/block-backend.c | 10 ++++++----
>  2 files changed, 10 insertions(+), 5 deletions(-)
> 
> -- 
> 2.13.6
> 

Reviewed-by: Fam Zheng <famz@redhat.com>

      parent reply	other threads:[~2017-11-20 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 14:11 [Qemu-devel] [PATCH for-2.11 0/2] Fix 'qemu-img info' on mirror target Kevin Wolf
2017-11-20 14:11 ` [Qemu-devel] [PATCH for-2.11 1/2] block: Don't use BLK_PERM_CONSISTENT_READ for format probing Kevin Wolf
2017-11-20 14:11 ` [Qemu-devel] [PATCH for-2.11 2/2] block: Don't request I/O permission with BDRV_O_NO_IO Kevin Wolf
2017-11-20 14:41   ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-11-20 14:22 ` Fam Zheng [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=20171120142238.GA6828@lemon.lan \
    --to=famz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.