From: David Gibson <david@gibson.dropbear.id.au>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PATCH 2/3] Allow larger return values from get_image_size()
Date: Mon, 27 Feb 2012 19:27:41 +1100 [thread overview]
Message-ID: <20120227082741.GI3433@truffala.fritz.box> (raw)
In-Reply-To: <m3sjhwwut6.fsf@blackfin.pond.sub.org>
On Mon, Feb 27, 2012 at 09:21:25AM +0100, Markus Armbruster wrote:
> David Gibson <david@gibson.dropbear.id.au> writes:
>
> > Currently get_image_size(), used to find the size of files, returns an int.
> > But for modern systems, int may be only 32-bit and we can have files
> > larger than that.
> >
> > This patch, therefore, changes the return type of get_image_size() to off_t
> > (the same as the return type from lseek() itself). It also audits all the
> > callers of get_image_size() to make sure they process the new unsigned
> > return type correctly.
> >
> > This leaves load_image_targphys() with a limited return type, but one thing
> > at a time (that function has far more callers to be audited, so it will
> > take longer to fix).
>
> I'm afraid this replaces the single, well-known integer overflow in
> get_image_size()'s conversion of lseek() value to int by many unknown
> overflows in get_image_size()'s users. One example below. Didn't look
> for more.
>
> If you need a wider get_image_size(), please make sure its users are
> prepared for it!
Actually, I have no such need at all, but when I fixed another bug in
loader.c, someone whinged about me not changing get_image_size(), so
here it is.
> Is the any use for image sizes exceeding size_t? Arent such images
> impossible to load?
Well, possibly not.
>
> [...]
> > diff --git a/hw/pc.c b/hw/pc.c
> > index b9f4bc7..cb41955 100644
> > --- a/hw/pc.c
> > +++ b/hw/pc.c
> > @@ -672,7 +672,8 @@ static void load_linux(void *fw_cfg,
> > target_phys_addr_t max_ram_size)
> > {
> > uint16_t protocol;
> > - int setup_size, kernel_size, initrd_size = 0, cmdline_size;
> > + int setup_size, kernel_size, cmdline_size;
> > + off_t initrd_size = 0;
> > uint32_t initrd_max;
> > uint8_t header[8192], *setup, *kernel, *initrd_data;
> > target_phys_addr_t real_addr, prot_addr, cmdline_addr, initrd_addr = 0;
> > @@ -795,7 +796,7 @@ static void load_linux(void *fw_cfg,
> > }
> >
> > initrd_size = get_image_size(initrd_filename);
> > - if (initrd_size < 0) {
> > + if (initrd_size == -1) {
>
> Needless churn.
No, it's not. Now that initrd_size is unsigned initrd_size < 0 would
return false always (and give a "comparison is always false due to
limited range of data type" warning).
>
> > fprintf(stderr, "qemu: error reading initrd %s\n",
> > initrd_filename);
> > exit(1);
> }
>
> initrd_addr = (initrd_max-initrd_size) & ~4095;
>
> initrd_data = g_malloc(initrd_size);
>
> Integer overflow in conversion from off_t initrd_size to the argument
> type size_t[*].
Hm, true.
Ok, well, I give up. Someone who actually needs it can fix it.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-02-27 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 0:36 [Qemu-devel] [0/3] Various code cleanups David Gibson
2012-02-24 0:36 ` [Qemu-devel] [PATCH 1/3] pci: Factor out bounds checking on config space accesses David Gibson
2012-02-24 0:36 ` [Qemu-devel] [PATCH 2/3] Allow larger return values from get_image_size() David Gibson
2012-02-24 0:48 ` Michael S. Tsirkin
2012-02-24 9:15 ` Andreas Färber
2012-02-24 22:08 ` David Gibson
2012-02-27 8:21 ` Markus Armbruster
2012-02-27 8:27 ` David Gibson [this message]
2012-02-27 9:31 ` Markus Armbruster
2012-02-24 0:36 ` [Qemu-devel] [PATCH 3/3] .gitignore update David Gibson
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=20120227082741.GI3433@truffala.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=anthony@codemonkey.ws \
--cc=armbru@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).