qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Naphtali Sprei <nsprei@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Fix qemu-img can't create qcow image based on	read-only image
Date: Fri, 29 Jan 2010 10:13:21 +0800	[thread overview]
Message-ID: <201001291013.21329.sheng@linux.intel.com> (raw)
In-Reply-To: <4B615622.8090902@redhat.com>

On Thursday 28 January 2010 17:17:22 Kevin Wolf wrote:
> Am 28.01.2010 06:22, schrieb Sheng Yang:
> > Commit 03cbdac7 "Disable fall-back to read-only when cannot open drive's
> > file for read-write" result in read-only image can't be used as backed
> > image in qemu-img.
> >
> > CC: Naphtali Sprei <nsprei@redhat.com>
> > Signed-off-by: Sheng Yang <sheng@linux.intel.com>
> > ---
> >
> > This issue blocked our QA's KVM nightly test. But in fact, I don't like
> > this patch, feeling uncomfortable to change long existed interface... Any
> > alternative? Add a readonly command line would change the default
> > behavior(I don't think fall back to readonly looks like a bug); or even
> > revert the commit? What's the story behind it?
> >
> >  qemu-img.c |   15 ++++++++++-----
> >  1 files changed, 10 insertions(+), 5 deletions(-)
> >
> > diff --git a/qemu-img.c b/qemu-img.c
> > index 3cea8ce..f8be5cb 100644
> > --- a/qemu-img.c
> > +++ b/qemu-img.c
> > @@ -188,11 +188,13 @@ static int read_password(char *buf, int buf_size)
> >  #endif
> >
> >  static BlockDriverState *bdrv_new_open(const char *filename,
> > -                                       const char *fmt)
> > +                                       const char *fmt,
> > +                                       int readonly)
> >  {
> >      BlockDriverState *bs;
> >      BlockDriver *drv;
> >      char password[256];
> > +    int flags = BRDV_O_FLAGS;
> >
> >      bs = bdrv_new("");
> >      if (!bs)
> > @@ -204,7 +206,10 @@ static BlockDriverState *bdrv_new_open(const char
> > *filename, } else {
> >          drv = NULL;
> >      }
> > -    if (bdrv_open2(bs, filename, BRDV_O_FLAGS | BDRV_O_RDWR, drv) < 0) {
> > +    if (!readonly) {
> > +        flags |= BDRV_O_RDWR;
> > +    }
> > +    if (bdrv_open2(bs, filename, flags, drv) < 0) {
> >          error("Could not open '%s'", filename);
> >      }
> >      if (bdrv_is_encrypted(bs)) {
> > @@ -343,7 +348,7 @@ static int img_create(int argc, char **argv)
> >                  }
> >              }
> >
> > -            bs = bdrv_new_open(backing_file->value.s, fmt);
> > +            bs = bdrv_new_open(backing_file->value.s, fmt, 1);
> >              bdrv_get_geometry(bs, &size);
> >              size *= 512;
> >              bdrv_delete(bs);
> > @@ -627,7 +632,7 @@ static int img_convert(int argc, char **argv)
> >
> >      total_sectors = 0;
> >      for (bs_i = 0; bs_i < bs_n; bs_i++) {
> > -        bs[bs_i] = bdrv_new_open(argv[optind + bs_i], fmt);
> > +        bs[bs_i] = bdrv_new_open(argv[optind + bs_i], fmt, 0);
> 
> Shouldn't it be read-only here, too?
 
Yes. 

Seems you guys are OK with this solution(and I think it's reasonable to remove 
the fall back). I would update the patch, hopefully it can be applied soon and 
picked up by Marcelo to resolve our block issue...

-- 
regards
Yang, Sheng

  reply	other threads:[~2010-01-29  2:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28  5:22 [Qemu-devel] [PATCH] Fix qemu-img can't create qcow image based on read-only image Sheng Yang
2010-01-28  9:17 ` Kevin Wolf
2010-01-29  2:13   ` Sheng Yang [this message]
2010-01-28  9:40 ` [Qemu-devel] " Naphtali Sprei

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=201001291013.21329.sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=nsprei@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 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).