qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Josh Durgin <josh.durgin@dreamhost.com>
Cc: ceph-devel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [qemu-iotests][PATCH] Update rbd support
Date: Thu, 21 Apr 2011 08:49:16 +0200	[thread overview]
Message-ID: <20110421064916.GA2606@lst.de> (raw)
In-Reply-To: <c87587fab7b312c58c7d59ac6117eff5@hq.newdream.net>

On Tue, Apr 12, 2011 at 10:42:00PM -0700, Josh Durgin wrote:
> > I suspect we only support the weird writing past size for the
> > file protocol, so we should only run the test for it.
> > 
> > Or does sheepdog do anything special about it?
> 
> Sheepdog supports it by truncating to the right size if a write
> would be past the end. I'm not sure if other protocols support
> it.

I've changed 016 to require the file or sheepdog protocols, and then
applied the rest of your patch.  Thanks a lot!

      reply	other threads:[~2011-04-21  6:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  0:45 [Qemu-devel] [PATCH v3 0/4] rbd improvements Josh Durgin
2011-04-13  0:45 ` [Qemu-devel] [PATCH v3 1/4] rbd: use the higher level librbd instead of just librados Josh Durgin
2011-04-13  0:45 ` [Qemu-devel] [PATCH v3 2/4] rbd: allow configuration of rados from the rbd filename Josh Durgin
2011-04-13  0:45 ` [Qemu-devel] [PATCH v3 3/4] rbd: check return values when scheduling aio Josh Durgin
2011-04-13  0:45 ` [Qemu-devel] [PATCH v3 4/4] rbd: Add bdrv_truncate implementation Josh Durgin
2011-04-13  0:47 ` [Qemu-devel] [qemu-iotests][PATCH] Update rbd support Josh Durgin
2011-04-13  2:43   ` Christoph Hellwig
2011-04-13  5:42     ` Josh Durgin
2011-04-21  6:49       ` Christoph Hellwig [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=20110421064916.GA2606@lst.de \
    --to=hch@lst.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@dreamhost.com \
    --cc=kvm@vger.kernel.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 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).