From: Kashyap Chamarthy <kchamart@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
stefanha@redhat.com, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 2/2] qemu-img: Document --force-share / -U
Date: Tue, 30 Jan 2018 15:34:47 +0100 [thread overview]
Message-ID: <20180130143447.quqbwpitu3iau2qv@eukaryote> (raw)
In-Reply-To: <b552c5fb-f79a-98f1-bac7-26cf6e106f06@redhat.com>
On Tue, Jan 30, 2018 at 08:23:50AM -0600, Eric Blake wrote:
> On 01/30/2018 12:34 AM, Fam Zheng wrote:
[...]
> > +If specified, @code{qemu-img} will open the image in shared mode, allowing
> > +concurrent writers. For example, this can be used to get the image information
>
> Actually, we only permit one writer at a time. Would it be better to
> say "allowing a concurrent writer"?
Definitely worth rewording. Otherwise the two sentences:
"If specified, @code{qemu-img} will open the image in shared mode,
allowing concurrent writers."
"This option is only allowed when opening images in read-only mode."
are at odds with each other --- it says "concurrent writers" are
allowed, BUT "allowed only when opening images in 'read-only' mode".
> > +(with 'info' subcommand) when the image is used by a running guest. Note that
> > +this could produce inconsistent results because of concurrent metadata changes,
> > +etc. This option is only allowed when opening images in read-only mode.
>
> After all, we are stating that this process (which must be read-only,
> because we can't have two writers at once) is permitting some other
> process to be the concurrent writer (but not multiple processes to be
> concurrent writers)
Precisely. So it's worth being clearer.
With the rewording suggested by Eric:
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
--
/kashyap
next prev parent reply other threads:[~2018-01-30 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 6:34 [Qemu-devel] [PATCH v6 0/2] qemu-img: Document --force-share / -U Fam Zheng
2018-01-30 6:34 ` [Qemu-devel] [PATCH v6 1/2] qemu-img.texi: Clean up parameter list Fam Zheng
2018-01-30 13:50 ` Eric Blake
2018-01-30 6:34 ` [Qemu-devel] [PATCH v6 2/2] qemu-img: Document --force-share / -U Fam Zheng
2018-01-30 12:14 ` Stefan Hajnoczi
2018-01-30 13:52 ` Eric Blake
2018-01-30 14:23 ` Eric Blake
2018-01-30 14:34 ` Kashyap Chamarthy [this message]
2018-01-30 16:38 ` Kevin Wolf
2018-01-31 14:12 ` Stefan Hajnoczi
2018-01-31 14:22 ` Kevin Wolf
2018-02-01 11:44 ` Stefan Hajnoczi
2018-02-09 3:29 ` Fam Zheng
2018-02-09 3:31 ` 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=20180130143447.quqbwpitu3iau2qv@eukaryote \
--to=kchamart@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).