All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	kchamart@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2] qemu-img: Document --force-share / -U
Date: Mon, 11 Dec 2017 17:30:41 +0800	[thread overview]
Message-ID: <20171211093041.GB3350@lemon> (raw)
In-Reply-To: <20171208095412.GC23880@stefanha-x1.localdomain>

On Fri, 12/08 09:54, Stefan Hajnoczi wrote:
> On Fri, Dec 08, 2017 at 09:44:56AM +0800, Fam Zheng wrote:
> > +@item --force-share (-U)
> > +
> > +If specified, @code{qemu-img} will open the image with shared permissions,
> > +which makes it less likely to conflict with a running guest's permissions due
> > +to image locking. For example, this can be used to get the image information
> > +(with 'info' subcommand) when the image is used by a running guest. Note that
> > +this could produce inconsistent result because of concurrent metadata changes,
> > +etc.
> 
> The documentation isn't clear on whether read-write is supported or just
> read-only.

block.c will emit an error if used with read-write. I will add a sentence for
that.

Fam

  parent reply	other threads:[~2017-12-11  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  1:44 [Qemu-devel] [PATCH v2] qemu-img: Document --force-share / -U Fam Zheng
2017-12-08  9:54 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-12-08 11:47   ` Kevin Wolf
2017-12-11  9:30   ` Fam Zheng [this message]
2017-12-11  9:05 ` [Qemu-devel] " Kashyap Chamarthy

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=20171211093041.GB3350@lemon \
    --to=famz@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 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.