From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: Fix access after end of array
Date: Fri, 19 Feb 2010 16:01:40 -0600 [thread overview]
Message-ID: <4B7F0A44.6060609@codemonkey.ws> (raw)
In-Reply-To: <1266332089-14381-1-git-send-email-kwolf@redhat.com>
On 02/16/2010 08:54 AM, Kevin Wolf wrote:
> If a write requests crosses a L2 table boundary and all clusters until the
> end of the L2 table are usable for the request, we must not look at the next
> L2 entry because we already have arrived at the end of the array.
>
> Signed-off-by: Kevin Wolf<kwolf@redhat.com>
>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
> block/qcow2-cluster.c | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/block/qcow2-cluster.c b/block/qcow2-cluster.c
> index 3501a94..b13b693 100644
> --- a/block/qcow2-cluster.c
> +++ b/block/qcow2-cluster.c
> @@ -750,12 +750,15 @@ int qcow2_alloc_cluster_offset(BlockDriverState *bs, uint64_t offset,
> while (i< nb_clusters) {
> i += count_contiguous_clusters(nb_clusters - i, s->cluster_size,
> &l2_table[l2_index], i, 0);
> -
> - if(be64_to_cpu(l2_table[l2_index + i]))
> + if ((i>= nb_clusters) || be64_to_cpu(l2_table[l2_index + i])) {
> break;
> + }
>
> i += count_contiguous_free_clusters(nb_clusters - i,
> &l2_table[l2_index + i]);
> + if (i>= nb_clusters) {
> + break;
> + }
>
> cluster_offset = be64_to_cpu(l2_table[l2_index + i]);
>
> @@ -763,6 +766,7 @@ int qcow2_alloc_cluster_offset(BlockDriverState *bs, uint64_t offset,
> (cluster_offset& QCOW_OFLAG_COMPRESSED))
> break;
> }
> + assert(i<= nb_clusters);
> nb_clusters = i;
>
> /*
>
prev parent reply other threads:[~2010-02-19 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 14:54 [Qemu-devel] [PATCH] qcow2: Fix access after end of array Kevin Wolf
2010-02-19 22:01 ` Anthony Liguori [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=4B7F0A44.6060609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@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).