From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: John Snow <jsnow@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, qemu-devel@nongnu.org,
qemu-stable@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
den@openvz.org
Subject: Re: [PATCH] block/io: fix bdrv_co_do_copy_on_readv
Date: Fri, 13 Mar 2020 09:42:17 +0300 [thread overview]
Message-ID: <b4cb7822-bcbe-15d8-3c45-c32a1a248b02@virtuozzo.com> (raw)
In-Reply-To: <ba1cdff0-3dba-36b5-9a55-1394e3800404@redhat.com>
13.03.2020 2:09, John Snow wrote:
>
>
> On 3/12/20 4:19 AM, Vladimir Sementsov-Ogievskiy wrote:
>> Prior to 1143ec5ebf4 it was OK to qemu_iovec_from_buf() from aligned-up
>> buffer to original qiov, as qemu_iovec_from_buf() will stop at qiov end
>> anyway.
>>
>> But after 1143ec5ebf4 we assume that bdrv_co_do_copy_on_readv works on
>> part of original qiov, defined by qiov_offset and bytes. So we must not
>> touch qiov behind qiov_offset+bytes bound. Fix it.
>>
>
> For the purposes of the stable branch commit log, how does the bug
> manifest? Are there known cases? What's the impact?
>
> (Do we have tests?)
Sorry, nothing of these things. I just saw it while working with this code.
>
>> Cc: qemu-stable@nongnu.org # v4.2
>> Fixes: 1143ec5ebf4
>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>> ---
>> block/io.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/block/io.c b/block/io.c
>> index 7e4cb74cf4..aba67f66b9 100644
>> --- a/block/io.c
>> +++ b/block/io.c
>> @@ -1399,7 +1399,7 @@ static int coroutine_fn bdrv_co_do_copy_on_readv(BdrvChild *child,
>> if (!(flags & BDRV_REQ_PREFETCH)) {
>> qemu_iovec_from_buf(qiov, qiov_offset + progress,
>> bounce_buffer + skip_bytes,
>> - pnum - skip_bytes);
>> + MIN(pnum - skip_bytes, bytes - progress));
>> }
>> } else if (!(flags & BDRV_REQ_PREFETCH)) {
>> /* Read directly into the destination */
>>
> Even if I don't understand the bug, the tighter bound seems provably
> correct anyway, so...
>
> Reviewed-by: John Snow <jsnow@redhat.com>
>
Thanks!
--
Best regards,
Vladimir
next prev parent reply other threads:[~2020-03-13 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 8:19 [PATCH] block/io: fix bdrv_co_do_copy_on_readv Vladimir Sementsov-Ogievskiy
2020-03-12 23:09 ` John Snow
2020-03-13 6:42 ` Vladimir Sementsov-Ogievskiy [this message]
2020-03-16 11:46 ` 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=b4cb7822-bcbe-15d8-3c45-c32a1a248b02@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).