From: Kevin Wolf <kwolf@redhat.com>
To: Kevin Shanahan <kmshanah@disenchant.net>
Cc: libvir-list@redhat.com, Michael Tokarev <mjt@tls.msk.ru>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] blockdev: preserve readonly and snapshot states across media changes
Date: Fri, 21 Sep 2012 09:11:22 +0200 [thread overview]
Message-ID: <505C131A.2030501@redhat.com> (raw)
In-Reply-To: <20120920232022.GA13110@tuon.disenchant.local>
Am 21.09.2012 01:20, schrieb Kevin Shanahan:
> If readonly=on is given at device creation time, the ->readonly flag
> needs to be set in the block driver state for this device so that
> readonly-ness is preserved across media changes (qmp change command).
> Similarly, to preserve the snapshot property requires ->open_flags to
> be correct.
>
> Signed-off-by: Kevin Shanahan <kmshanah@disenchant.net>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2012-09-21 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 23:20 [Qemu-devel] [PATCH] blockdev: preserve readonly and snapshot states across media changes Kevin Shanahan
2012-09-21 7:11 ` Kevin Wolf [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=505C131A.2030501@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=kmshanah@disenchant.net \
--cc=libvir-list@redhat.com \
--cc=mjt@tls.msk.ru \
--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 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).