All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH RFC 0/3] block: Backdoor to skip image locking in qemu-io/qemu-img
Date: Thu, 13 Apr 2017 21:14:18 -0400	[thread overview]
Message-ID: <63a9a137-2709-f936-7c7a-f11ace8fdc51@redhat.com> (raw)
In-Reply-To: <20170314023933.12118-1-famz@redhat.com>



On 03/13/2017 10:39 PM, Fam Zheng wrote:
> Hi Kevin,
> 
> This tries to capture your idea to add a explicit command option in qemu-io and
> qemu-img for user to specify "expect inconsistent data when reading image".
> It's stored as a BDRV_O_ flag internally, I don't know if there is a cleaner
> way or not.
> 
> It's depended on by image locking series because several test cases need to be
> updated to use this flag.
> 
> Fam
> 
> Fam Zheng (3):
>   block: Introduce BDRV_O_UNSAFE_READ
>   qemu-img: Add --unsafe-read option to subcommands
>   qemu-io: Add --unsafe-read option
> 
>  block/block-backend.c |   2 +-
>  include/block/block.h |   1 +
>  qemu-img.c            | 148 ++++++++++++++++++++++++++++++++++++++------------
>  qemu-io.c             |  28 +++++++---
>  4 files changed, 137 insertions(+), 42 deletions(-)
> 

Month old with no replies or ping, DOA?

--js

  parent reply	other threads:[~2017-04-14  1:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14  2:39 [Qemu-devel] [PATCH RFC 0/3] block: Backdoor to skip image locking in qemu-io/qemu-img Fam Zheng
2017-03-14  2:39 ` [Qemu-devel] [PATCH RFC 1/3] block: Introduce BDRV_O_UNSAFE_READ Fam Zheng
2017-04-18 13:15   ` Eric Blake
2017-03-14  2:39 ` [Qemu-devel] [PATCH RFC 2/3] qemu-img: Add --unsafe-read option to subcommands Fam Zheng
2017-04-18 13:20   ` Eric Blake
2017-04-20  3:27     ` Fam Zheng
2017-03-14  2:39 ` [Qemu-devel] [PATCH RFC 3/3] qemu-io: Add --unsafe-read option Fam Zheng
2017-04-18 13:27   ` Eric Blake
2017-04-20  3:29     ` Fam Zheng
2017-04-14  1:14 ` John Snow [this message]
2017-04-14  2:25   ` [Qemu-devel] [Qemu-block] [PATCH RFC 0/3] block: Backdoor to skip image locking in qemu-io/qemu-img Fam Zheng

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=63a9a137-2709-f936-7c7a-f11ace8fdc51@redhat.com \
    --to=jsnow@redhat.com \
    --cc=famz@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.