qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-io: add flag to mark files growable
Date: Mon, 6 Jul 2009 12:51:11 +0200	[thread overview]
Message-ID: <20090706105111.GA9469@lst.de> (raw)
In-Reply-To: <4A51D486.10005@redhat.com>

On Mon, Jul 06, 2009 at 12:40:06PM +0200, Kevin Wolf wrote:
> Ok, you are right. raw was the only exception because it could be used
> as a protocol even though it didn't have a protocol name.
> 
> Looks fine to me then if you enforce the limitation instead of only
> printing an error message and opening the image anyway. Not printing the
> error and opening the image would be fine either. I just don't like
> error messages without errors.

Well, the primary use of qemu-iotests is to try out the I/O patterns,
and the -g option is to check out we do the correct thing for growable
files, so I'd really prefer it to fail if we're not allow to actually
make it growable.

Now one think I could do is to just add a growable flag to the
BlockDriver to make it explicit.  Currently only raw files (in the posix
and win32 flavours) would set it.  That would also fix the bug what we
currenly allow to grow host devices even if we can't.

  reply	other threads:[~2009-07-06 10:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-04 15:53 [Qemu-devel] [PATCH] qemu-io: add flag to mark files growable Christoph Hellwig
2009-07-06  8:53 ` Kevin Wolf
2009-07-06 10:20   ` Christoph Hellwig
2009-07-06 10:40     ` Kevin Wolf
2009-07-06 10:51       ` Christoph Hellwig [this message]
2009-07-06 11:04         ` Kevin Wolf
2009-07-06 11:14           ` Christoph Hellwig

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=20090706105111.GA9469@lst.de \
    --to=hch@lst.de \
    --cc=kwolf@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).