From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-aio: Allow reads beyond the end of growable images
Date: Fri, 14 Oct 2011 09:51:38 +0200 [thread overview]
Message-ID: <20111014075138.GA23272@lst.de> (raw)
In-Reply-To: <1318513779-8555-1-git-send-email-kwolf@redhat.com>
On Thu, Oct 13, 2011 at 03:49:39PM +0200, Kevin Wolf wrote:
> This is the linux-aio version of commits 22afa7b5 (raw-posix, synchronous) and
> ba1d1afd (posix-aio-compat). Reads now produce zeros after the end of file
> instead of failing or resulting in short reads, making linux-aio compatible
> with the behaviour of synchronous raw-posix requests and posix-aio-compat.
>
> The problem can be reproduced like this:
>
> dd if=/dev/zero of=/tmp/test.raw bs=1 count=1234
> ./qemu-io -k -n -g -c 'read -p 1024 512' /tmp/test.raw
Can you send a patch doing this for qemu-iotests?
prev parent reply other threads:[~2011-10-14 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:49 [Qemu-devel] [PATCH] linux-aio: Allow reads beyond the end of growable images Kevin Wolf
2011-10-13 14:55 ` Stefan Hajnoczi
2011-10-14 7:51 ` 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=20111014075138.GA23272@lst.de \
--to=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).