block/vpc: make checks on max table size a bit more lax
commit66176fc6a7b86fcead206fb0685ba688e40646a9
authorJeff Cody <jcody@redhat.com>
Wed, 23 Mar 2016 03:33:42 +0000 (22 23:33 -0400)
committerKevin Wolf <kwolf@redhat.com>
Fri, 15 Apr 2016 15:22:12 +0000 (15 17:22 +0200)
tree361bfc4b67259ecf9c1d8f3a5f13142b233eb27f
parentc23fb11bbba90da2a5e2e121fb391a608b82afe5
block/vpc: make checks on max table size a bit more lax

The check on the max_table_size field not being larger than required is
valid, and in accordance with the VHD spec.  However, there have been
VHD images encountered in the wild that have an out-of-spec max table
size that is technically too large.

There is no issue in allowing this larger table size, as we also
later verify that the computed size (used for the pagetable) is
large enough to fit all sectors.  In addition, max_table_entries
is bounds checked against SIZE_MAX and INT_MAX.

Remove the strict check, so that we can accomodate these sorts of
images that are benignly out of spec.

Reported-by: Stefan Hajnoczi <stefanha@redhat.com>
Reported-by: Grant Wu <grantwwu@gmail.com>
Signed-off-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
block/vpc.c