From: Kevin Wolf <kwolf@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2] block-vpc: Don't silently create smaller image than requested
Date: Thu, 09 Apr 2009 09:43:22 +0200 [thread overview]
Message-ID: <49DDA71A.7050307@redhat.com> (raw)
In-Reply-To: <20090408225316.GA23493@volta.aurel32.net>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Aurelien Jarno schrieb:
> On Wed, Apr 08, 2009 at 04:49:05PM +0200, Kevin Wolf wrote:
>> The algorithm from the VHD specification for CHS calculation silently limits
>> images to 127 GB which may confuse a user who requested a larger image. Better
>> output an error message and abort.
>>
>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>> ---
>> block-vpc.c | 9 ++++++---
>> qemu-img.c | 4 ++++
>> 2 files changed, 10 insertions(+), 3 deletions(-)
>>
>> diff --git a/block-vpc.c b/block-vpc.c
>> index 7ae5202..d915d20 100644
>> --- a/block-vpc.c
>> +++ b/block-vpc.c
>> @@ -433,14 +433,16 @@ static int vpc_write(BlockDriverState *bs, int64_t sector_num,
>> *
>> * Note that the geometry doesn't always exactly match total_sectors but
>> * may round it down.
>> + *
>> + * Returns 0 on success, -EFBIG if the size is larger than 127 GB
>> */
>
> Actually 0 is never returned, leading to a warning:
> CC block-vpc.o
> block-vpc.c: In function ‘calculate_geometry’:
> block-vpc.c:475: warning: control reaches end of non-void function
Oops, you're right. I'm pretty sure that it compiled fine when I tested
it. Maybe forgot to commit or something.
Please find attached a new version which actually contains a return 0.
Kevin
[-- Attachment #2: 0001-block-vpc-Don-t-silently-create-smaller-image-than.patch --]
[-- Type: text/plain, Size: 3078 bytes --]
From 9d612c70ee232443337c79825afd754aad1db878 Mon Sep 17 00:00:00 2001
From: Kevin Wolf <kwolf@redhat.com>
Date: Wed, 8 Apr 2009 15:44:04 +0200
Subject: [PATCH] block-vpc: Don't silently create smaller image than requested
The algorithm from the VHD specification for CHS calculation silently limits
images to 127 GB which may confuse a user who requested a larger image. Better
output an error message and abort.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
block-vpc.c | 11 ++++++++---
qemu-img.c | 4 ++++
2 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/block-vpc.c b/block-vpc.c
index 7ae5202..71a171d 100644
--- a/block-vpc.c
+++ b/block-vpc.c
@@ -433,14 +433,16 @@ static int vpc_write(BlockDriverState *bs, int64_t sector_num,
*
* Note that the geometry doesn't always exactly match total_sectors but
* may round it down.
+ *
+ * Returns 0 on success, -EFBIG if the size is larger than 127 GB
*/
-static void calculate_geometry(int64_t total_sectors, uint16_t* cyls,
+static int calculate_geometry(int64_t total_sectors, uint16_t* cyls,
uint8_t* heads, uint8_t* secs_per_cyl)
{
uint32_t cyls_times_heads;
if (total_sectors > 65535 * 16 * 255)
- total_sectors = 65535 * 16 * 255;
+ return -EFBIG;
if (total_sectors > 65535 * 16 * 63) {
*secs_per_cyl = 255;
@@ -470,6 +472,8 @@ static void calculate_geometry(int64_t total_sectors, uint16_t* cyls,
// Note: Rounding up deviates from the Virtual PC behaviour
// However, we need this to avoid truncating images in qemu-img convert
*cyls = (cyls_times_heads + *heads - 1) / *heads;
+
+ return 0;
}
static int vpc_create(const char *filename, int64_t total_sectors,
@@ -493,7 +497,8 @@ static int vpc_create(const char *filename, int64_t total_sectors,
return -EIO;
// Calculate matching total_size and geometry
- calculate_geometry(total_sectors, &cyls, &heads, &secs_per_cyl);
+ if (calculate_geometry(total_sectors, &cyls, &heads, &secs_per_cyl))
+ return -EFBIG;
total_sectors = (int64_t) cyls * heads * secs_per_cyl;
// Prepare the Hard Disk Footer
diff --git a/qemu-img.c b/qemu-img.c
index 913ad34..ccf4a6f 100644
--- a/qemu-img.c
+++ b/qemu-img.c
@@ -306,6 +306,8 @@ static int img_create(int argc, char **argv)
if (ret < 0) {
if (ret == -ENOTSUP) {
error("Formatting or formatting option not supported for file format '%s'", fmt);
+ } else if (ret == -EFBIG) {
+ error("The image size is too large for file format '%s'", fmt);
} else {
error("Error while formatting");
}
@@ -494,6 +496,8 @@ static int img_convert(int argc, char **argv)
if (ret < 0) {
if (ret == -ENOTSUP) {
error("Formatting not supported for file format '%s'", out_fmt);
+ } else if (ret == -EFBIG) {
+ error("The image size is too large for file format '%s'", out_fmt);
} else {
error("Error while formatting '%s'", out_filename);
}
--
1.6.0.6
next prev parent reply other threads:[~2009-04-09 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 14:49 [Qemu-devel] [PATCH] block-vpc: Don't silently create smaller image than requested Kevin Wolf
2009-04-08 22:53 ` Aurelien Jarno
2009-04-09 7:43 ` Kevin Wolf [this message]
2009-04-15 14:45 ` [Qemu-devel] [PATCH v2] " Aurelien Jarno
2009-04-18 15:41 ` [Qemu-devel] [PATCH] " Anthony Liguori
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=49DDA71A.7050307@redhat.com \
--to=kwolf@redhat.com \
--cc=aurelien@aurel32.net \
--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).