From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: Fix error handling for immediate backing file read failure
Date: Wed, 09 Feb 2011 10:12:46 +0100 [thread overview]
Message-ID: <4D525A8E.40407@redhat.com> (raw)
In-Reply-To: <m3hbcepgkj.fsf@blackfin.pond.sub.org>
Am 08.02.2011 18:43, schrieb Markus Armbruster:
> Kevin Wolf <kwolf@redhat.com> writes:
>
>> Requests could return success even though they failed when bdrv_aio_readv
>> returned NULL for a backing file read.
>>
>> Reported-by: Chunqiang Tang <ctang@us.ibm.com>
>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>> ---
>> block/qcow2.c | 4 +++-
>> 1 files changed, 3 insertions(+), 1 deletions(-)
>>
>> diff --git a/block/qcow2.c b/block/qcow2.c
>> index 28338bf..647c2a4 100644
>> --- a/block/qcow2.c
>> +++ b/block/qcow2.c
>> @@ -479,8 +479,10 @@ static void qcow2_aio_read_cb(void *opaque, int ret)
>> BLKDBG_EVENT(bs->file, BLKDBG_READ_BACKING_AIO);
>> acb->hd_aiocb = bdrv_aio_readv(bs->backing_hd, acb->sector_num,
>> &acb->hd_qiov, n1, qcow2_aio_read_cb, acb);
>> - if (acb->hd_aiocb == NULL)
>> + if (acb->hd_aiocb == NULL) {
>> + ret = -EIO;
>> goto done;
>> + }
>> } else {
>> ret = qcow2_schedule_bh(qcow2_aio_read_bh, acb);
>> if (ret < 0)
>
> Good catch.
>
> Nearby
>
> if (qcow2_decompress_cluster(bs, acb->cluster_offset) < 0)
> goto done;
>
> looks suspicious to my ignorant eyes. Is it okay?
No, it's wrong as well, and it's the second part of Chunquiang Tang's
bug report. I started a patch for it yesterday, but didn't have time to
test it because I didn't expect my train to wait. ;-) I'll send it today.
Kevin
prev parent reply other threads:[~2011-02-09 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 17:15 [Qemu-devel] [PATCH] qcow2: Fix error handling for immediate backing file read failure Kevin Wolf
2011-02-08 17:43 ` Markus Armbruster
2011-02-09 9:12 ` 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=4D525A8E.40407@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@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).