From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Do not execute 052 with -nocache
Date: Tue, 24 Sep 2013 16:58:55 +0200 [thread overview]
Message-ID: <20130924145855.GC3011@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1379947113-12476-1-git-send-email-mreitz@redhat.com>
Am 23.09.2013 um 16:38 hat Max Reitz geschrieben:
> Test 052 uses qemu-io -s which will result in bdrv_open trying to create
> a temporary snapshot file in /tmp. However, since O_DIRECT and tmpfs
> do not work well together, disable this test for -nocache.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2013-09-24 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 14:38 [Qemu-devel] [PATCH] qemu-iotests: Do not execute 052 with -nocache Max Reitz
2013-09-24 11:32 ` Stefan Hajnoczi
2013-09-24 14:58 ` Kevin Wolf [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=20130924145855.GC3011@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).