| commit | 59d6ee485020fdc45cb0f9f748d8b8850fad9f8c | |
| author | Sam Eiderman <shmuel.eiderman@oracle.com> | |
| Thu, 20 Jun 2019 09:10:56 +0000 (20 12:10 +0300) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Mon, 24 Jun 2019 13:53:02 +0000 (24 15:53 +0200) | ||
| tree | 4900f29e776a3e46836343141345daa4f5f6cde7 | treesnapshot (tar.gz zip) |
| parent | 940a2cd5d2eede3c81b83712c55cc6d3c5e6c463 | commitdiff |
vmdk: Reduce the max bound for L1 table size
512M of L1 entries is a very loose bound, only 32M are required to store
the maximal supported VMDK file size of 2TB.
Fixed qemu-iotest 59# - now failure occures before on impossible L1
table size.
Reviewed-by: Karl Heubaum <karl.heubaum@oracle.com>
Reviewed-by: Eyal Moscovici <eyal.moscovici@oracle.com>
Reviewed-by: Liran Alon <liran.alon@oracle.com>
Reviewed-by: Arbel Moshe <arbel.moshe@oracle.com>
Signed-off-by: Sam Eiderman <shmuel.eiderman@oracle.com>
Message-id: 20190620091057.47441-3-shmuel.eiderman@oracle.com
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
512M of L1 entries is a very loose bound, only 32M are required to store
the maximal supported VMDK file size of 2TB.
Fixed qemu-iotest 59# - now failure occures before on impossible L1
table size.
Reviewed-by: Karl Heubaum <karl.heubaum@oracle.com>
Reviewed-by: Eyal Moscovici <eyal.moscovici@oracle.com>
Reviewed-by: Liran Alon <liran.alon@oracle.com>
Reviewed-by: Arbel Moshe <arbel.moshe@oracle.com>
Signed-off-by: Sam Eiderman <shmuel.eiderman@oracle.com>
Message-id: 20190620091057.47441-3-shmuel.eiderman@oracle.com
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
| block/vmdk.c | diffblobblamehistory | |
| tests/qemu-iotests/059.out | diffblobblamehistory |