qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liam Merwick <liam.merwick@oracle.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 8/8] qcow2: Read outside array bounds in qcow2_pre_write_overlap_check()
Date: Fri, 31 Aug 2018 19:16:01 +0100	[thread overview]
Message-ID: <189770df-99cb-162d-007b-bdb48dd29a7c@oracle.com> (raw)
In-Reply-To: <8d2e5805-2d53-3c20-c34a-514614750dec@redhat.com>



On 31/08/18 17:53, Eric Blake wrote:
> On 08/31/2018 11:36 AM, Liam Merwick wrote:
>> The commit for 0e4e4318eaa5 increments QCOW2_OL_MAX_BITNR but does not
>> add an array entry for QCOW2_OL_BITMAP_DIRECTORY_BITNR to 
>> metadata_ol_names[].
>> As a result, an array dereference of metadata_ol_names[8] in
>> qcow2_pre_write_overlap_check() could result in a read outside of the 
>> array bounds.
>>
>> Fixes: 0e4e4318eaa5 ('qcow2: add overlap check for bitmap directory')
>>
>> Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>> Signed-off-by: Liam Merwick <Liam.Merwick@oracle.com>
>> ---
>>   block/qcow2-refcount.c | 26 ++++++++++++++++++--------
>>   1 file changed, 18 insertions(+), 8 deletions(-)
>>
> 
>> +
>> +/*
>> + * Catch at compile time the case where an overlap detection bit
>> + * was added to QCow2MetadataOverlap in block/qcow2.h but a
>> + * corresponding entry to metadata_ol_names[] wasn't added.
>> + */
> 
> I'm not sure the comment adds much value.  I'd be fine with dropping it.
> 
>> +QEMU_BUILD_BUG_ON(QCOW2_OL_MAX_BITNR !=
>> +    (sizeof(metadata_ol_names) / sizeof(metadata_ol_names[0])));
> 
> We have a macro for that.  Spell this:
> 
> QEMU_BUILD_BUG_ON(QCOW2_OL_MAX_BITNR != ARRAY_SIZE(metadata_ol_names));
> 
> and then you can have
> 
> Reviewed-by: Eric Blake <eblake@redhat.com>
> 

Thanks, I've updated those and removed the double space in patch6. Will 
be in upcoming v3

Regards,
Liam

      reply	other threads:[~2018-08-31 18:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 16:36 [Qemu-devel] [PATCH v2 0/8] off-by-one and NULL pointer accesses detected by static analysis Liam Merwick
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 1/8] configure: Provide option to explicitly disable AVX2 Liam Merwick
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 2/8] job: Fix off-by-one assert checks for JobSTT and JobVerbTable Liam Merwick
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 3/8] block: Null pointer dereference in blk_root_get_parent_desc() Liam Merwick
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 4/8] qemu-img: potential Null pointer deref in img_commit() Liam Merwick
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 5/8] block: Fix potential Null pointer dereferences in vvfat.c Liam Merwick
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 6/8] block: dump_qlist() may dereference a Null pointer Liam Merwick
2018-08-31 16:47   ` Eric Blake
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 7/8] io: potential unnecessary check in qio_channel_command_new_spawn() Liam Merwick
2018-08-31 16:48   ` Eric Blake
2018-08-31 16:36 ` [Qemu-devel] [PATCH v2 8/8] qcow2: Read outside array bounds in qcow2_pre_write_overlap_check() Liam Merwick
2018-08-31 16:53   ` Eric Blake
2018-08-31 18:16     ` Liam Merwick [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=189770df-99cb-162d-007b-bdb48dd29a7c@oracle.com \
    --to=liam.merwick@oracle.com \
    --cc=eblake@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).