From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
qemu-block@nongnu.org, mreitz@redhat.com, qemu-devel@nongnu.org,
cornelia.huck@de.ibm.com, pasic@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH RFC 1/1] block: Handle NULL options correctly in raw_open
Date: Wed, 8 Mar 2017 17:31:05 +0800 [thread overview]
Message-ID: <20170308093105.GC7563@bjsdjshi@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170308091346.GB5211@noname.redhat.com>
* Kevin Wolf <kwolf@redhat.com> [2017-03-08 10:13:46 +0100]:
> Am 08.03.2017 um 03:15 hat Dong Jia Shi geschrieben:
> > A normal call for raw_open should always pass in a non-NULL @options,
> > but for some certain cases (e.g. trying to applying snapshot on a RBD
> > image), they call raw_open with a NULL @options right after the calling
> > for raw_close.
> >
> > Let's take the NULL @options as a sign of trying to do raw_open again,
> > and just simply return a success code.
> >
> > Signed-off-by: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
>
> I think we rather need to fix bdrv_snapshot_goto() so that it doesn't
> pass NULL, but the actual options that were given for the node (i.e.
> bs->options).
I've tried that before the current try. bs->options does not have the
"file" key-value pair, so that leads to a fail too. Should we put "file"
in to the options manually? I noticed that it was removed from
bs->options during the calling of bdrv_open_inherit.
>
> Kevin
>
--
Dong Jia
next prev parent reply other threads:[~2017-03-08 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 2:15 [Qemu-devel] [PATCH RFC 0/1] block: Handle NULL options correctly in raw_open Dong Jia Shi
2017-03-08 2:15 ` [Qemu-devel] [PATCH RFC 1/1] " Dong Jia Shi
2017-03-08 9:13 ` Kevin Wolf
2017-03-08 9:31 ` Dong Jia Shi [this message]
2017-03-13 3:31 ` Dong Jia Shi
2017-03-13 10:15 ` Kevin Wolf
2017-03-14 3:23 ` Dong Jia Shi
2017-03-20 1:39 ` Dong Jia Shi
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=20170308093105.GC7563@bjsdjshi@linux.vnet.ibm.com \
--to=bjsdjshi@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-block@nongnu.org \
--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.