From: Kevin Wolf <kwolf@redhat.com>
To: "Sebastian Färber" <sfaerber82@gmail.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, jdurgin@redhat.com,
jcody@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block/rbd: add .bdrv_reopen_prepare() stub
Date: Fri, 13 May 2016 10:45:48 +0200 [thread overview]
Message-ID: <20160513084548.GA5529@noname.redhat.com> (raw)
In-Reply-To: <3f8edd94-280c-8aa7-0f07-ab674ee4667b@gmail.com>
Am 13.05.2016 um 10:29 hat Sebastian Färber geschrieben:
> Add support for reopen() by adding the .bdrv_reopen_prepare() stub
>
> Signed-off-by: Sebastian Färber <sfaerber82@gmail.com>
> Tested-by: Sebastian Färber <sfaerber82@gmail.com>
> ---
> block/rbd.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/block/rbd.c b/block/rbd.c
> index 5bc5b32..5f121b5 100644
> --- a/block/rbd.c
> +++ b/block/rbd.c
> @@ -577,6 +577,14 @@ failed_opts:
> return r;
> }
>
> +/* Note that this will not re-establish a connection with the Ceph cluster
> + - it is effectively a NOP. */
> +static int qemu_rbd_reopen_prepare(BDRVReopenState *state,
> + BlockReopenQueue *queue, Error **errp)
> +{
> + return 0;
> +}
A correct reopen implementation must consider all options and flags that
.bdrv_open() looked at.
The options are okay, as both "filename" and "password-secret" aren't
things that we want to allow a reopen to change. However, in the flags
BDRV_O_NOCACHE makes a difference:
if (flags & BDRV_O_NOCACHE) {
rados_conf_set(s->cluster, "rbd_cache", "false");
} else {
rados_conf_set(s->cluster, "rbd_cache", "true");
}
A reopen must either update the setting, or if it can't (e.g. because
librbd doesn't support it) any attempt to change the flag must fail.
Kevin
next prev parent reply other threads:[~2016-05-13 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 8:29 [Qemu-devel] [PATCH] block/rbd: add .bdrv_reopen_prepare() stub Sebastian Färber
2016-05-13 8:45 ` Kevin Wolf [this message]
2016-05-17 10:03 ` Sebastian Färber
2016-05-17 14:00 ` Jason Dillaman
2016-05-17 18:48 ` Josh Durgin
2016-05-18 7:36 ` Sebastian Färber
2016-05-18 8:19 ` Kevin Wolf
2016-05-18 15:54 ` Jason Dillaman
2016-05-18 5:31 ` Jeff Cody
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=20160513084548.GA5529@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=jcody@redhat.com \
--cc=jdurgin@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sfaerber82@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 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).