From: Fam Zheng <famz@redhat.com>
To: Philipp Hahn <hahn@univention.de>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] docs: Add image locking subsection
Date: Fri, 24 Nov 2017 16:43:59 +0800 [thread overview]
Message-ID: <20171124084359.GE3108@lemon> (raw)
In-Reply-To: <e36d9628-ce26-b019-3573-f1c358467d05@univention.de>
On Thu, 11/23 17:07, Philipp Hahn wrote:
> Hello,
>
> Am 23.11.2017 um 14:59 schrieb Fam Zheng:
> > diff --git a/docs/qemu-block-drivers.texi b/docs/qemu-block-drivers.texi
> > index 1cb1e55686..fa2e90d15f 100644
> > --- a/docs/qemu-block-drivers.texi
> > +++ b/docs/qemu-block-drivers.texi
> > @@ -785,6 +785,42 @@ warning: ssh server @code{ssh.example.com:22} does not support fsync
> ...
> > +To check if image locking is active, check the output of "lslocks" command on
> > +host and see if there are locks held by QEMU process on the image file. More
> > +than one bytes could be locked by a QEMU instance, each byte of which reflects
>
> "one byte", without the 's'?
>
> > +a perticular permission that are acquired or protected by the running block
>
> "particular", 'e' -> 'a'
>
Yes to both. Thanks!
Fam
next prev parent reply other threads:[~2017-11-24 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 13:59 [Qemu-devel] [PATCH 0/2] docs: Add documentation for image locking Fam Zheng
2017-11-23 13:59 ` [Qemu-devel] [PATCH 1/2] docs: Add image locking subsection Fam Zheng
2017-11-23 16:07 ` Philipp Hahn
2017-11-24 8:43 ` Fam Zheng [this message]
2017-11-23 17:01 ` Kevin Wolf
2017-11-24 8:43 ` Fam Zheng
2017-11-23 13:59 ` [Qemu-devel] [PATCH 2/2] qemu-options: Mention locking option of file driver Fam Zheng
2017-11-23 17:03 ` Kevin Wolf
2017-11-24 8:44 ` 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=20171124084359.GE3108@lemon \
--to=famz@redhat.com \
--cc=hahn@univention.de \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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.