From: Stefan Weil <weil@mail.berlios.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Blue Swirl <blauwirbel@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] bsd-user: Fix possible memory leaks
Date: Sun, 16 Jan 2011 16:27:49 +0100 [thread overview]
Message-ID: <4D330E75.9020806@mail.berlios.de> (raw)
In-Reply-To: <AANLkTim2oLDLu312EZgtjTSzTT0-Y90ZVgfmjvoqO_-t@mail.gmail.com>
Am 16.01.2011 15:07, schrieb Peter Maydell:
> On 16 January 2011 12:56, Stefan Weil <weil@mail.berlios.de> wrote:
>> diff --git a/bsd-user/elfload.c b/bsd-user/elfload.c
>> index 7374912..313ddc6 100644
>> --- a/bsd-user/elfload.c
>> +++ b/bsd-user/elfload.c
>> @@ -1072,11 +1072,16 @@ static void load_symbols(struct elfhdr *hdr,
>> int fd)
>> /* Now know where the strtab and symtab are. Snarf them. */
>> s = malloc(sizeof(*s));
>> syms = malloc(symtab.sh_size);
>> - if (!syms)
>> + if (!syms) {
>> + free(s);
>> return;
>> + }
>> s->disas_strtab = strings = malloc(strtab.sh_size);
>> - if (!s->disas_strtab)
>> + if (!s->disas_strtab) {
>> + free(s);
>> + free(syms);
>> return;
>> + }
>>
>> lseek(fd, symtab.sh_offset, SEEK_SET);
>> if (read(fd, syms, symtab.sh_size) != symtab.sh_size)
>
> Don't we also need to free s, syms and strings in the
> places later in the function where we return early
> (if read() calls fail)?
You are correct. cppcheck only reports the first location in a function.
I should have called it again after my modifications.
>
> The function also has an unchecked call to realloc().
>
> (All these things are handled correctly in the linux-user/
> version of this function.)
The realloc() is handled in linux-user, but not in a correct way.
A new version of my patch fixes the missing memory leaks
and realloc for bsd-user.
A second patch is needed to fix realloc for linux-user, too.
> Blue Swirl wrote:
>> If we used qemu_malloc(), this wouldn't happen since it will exit if
>> malloc() fails. But is that OK, maybe we want to load the file without
>> symbols then?
>
> AFAICT symbols are only used for debug tracing, so carrying
> on without them is a reasonable strategy. (Although if you
> fail a malloc this early on the chances of successfully running
> anything are not good, so it's a bit moot.)
>
> -- PMM
next prev parent reply other threads:[~2011-01-16 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 12:56 [Qemu-devel] [PATCH] bsd-user: Fix possible memory leaks Stefan Weil
2011-01-16 13:09 ` [Qemu-devel] " Blue Swirl
2011-01-16 14:07 ` [Qemu-devel] " Peter Maydell
2011-01-16 15:27 ` Stefan Weil [this message]
2011-01-16 15:28 ` [Qemu-devel] [PATCH v2] bsd-user: Fix possible memory leaks and wrong realloc call Stefan Weil
2011-01-17 20:24 ` [Qemu-devel] " Blue Swirl
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=4D330E75.9020806@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.org \
--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).