From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, eyakovlev@virtuozzo.com,
qemu-devel@nongnu.org, qemu-stable@nongnu.org,
pbonzini@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH for-2.8] block: Don't mark node clean after failed flush
Date: Mon, 7 Nov 2016 13:14:12 +0000 [thread overview]
Message-ID: <20161107131412.GL5036@stefanha-x1.localdomain> (raw)
In-Reply-To: <1478300595-10090-1-git-send-email-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Sat, Nov 05, 2016 at 12:03:15AM +0100, Kevin Wolf wrote:
> Commit 3ff2f67a changed bdrv_co_flush() so that no flush is issues if
> the image hasn't been dirtied since the last flush. This is not quite
> correct: The condition should be that the image hasn't been dirtied
> since the last _successful_ flush. This patch changes the logic
> accordingly.
>
> Without this fix, subsequent bdrv_co_flush() calls would return success
> without actually doing anything even though the image is still dirty.
> The difference is visible in some blkdebug test cases where error
> messages incorrectly disappeared after commit 3ff2f67a.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/io.c | 4 +++-
> tests/qemu-iotests/026.out | 22 ++++++++++++++++++++++
> tests/qemu-iotests/026.out.nocache | 22 ++++++++++++++++++++++
> tests/qemu-iotests/071.out | 2 ++
> 4 files changed, 49 insertions(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-11-07 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 23:03 [Qemu-devel] [PATCH for-2.8] block: Don't mark node clean after failed flush Kevin Wolf
2016-11-04 23:45 ` Denis V. Lunev
2016-11-07 13:14 ` Stefan Hajnoczi [this message]
2016-11-07 21:22 ` John Snow
2016-11-08 16:06 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=20161107131412.GL5036@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=den@openvz.org \
--cc=eyakovlev@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).