From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] xtensa: use g_malloc/g_new/g_free
Date: Mon, 08 May 2017 14:32:30 +0100 [thread overview]
Message-ID: <87r2zz8oep.fsf@linaro.org> (raw)
In-Reply-To: <20170508073529.23449-1-pbonzini@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Replace malloc/free with g_malloc/g_free to get a program exit on
> out of memory.
>
> Replace g_malloc with g_new when allocating the MemoryRegion to
> get more type safety.
>
> Reported by Coverity.
>
> Cc: Max Filippov <jcmvbkbc@gmail.com>
> Cc: qemu-trivial@nongnu.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> hw/xtensa/sim.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/xtensa/sim.c b/hw/xtensa/sim.c
> index d2d1d3a6fd..97307728f7 100644
> --- a/hw/xtensa/sim.c
> +++ b/hw/xtensa/sim.c
> @@ -41,13 +41,13 @@ static void xtensa_create_memory_regions(const XtensaMemory *memory,
> const char *name)
> {
> unsigned i;
> - char *num_name = malloc(strlen(name) + sizeof(i) * 3 + 1);
> + char *num_name = g_malloc(strlen(name) + sizeof(i) * 3 + 1);
It seems a little sketchy using the size of the storage type as a proxy
for the number of bytes used by the format specifier in a format string.
In this sort of situation I'd just use Glib and stop worrying about it:
GString num_name = g_string_new(NULL);
...
g_string_printf(num_name, "%s%u", name, i);
m = g_new(MemoryRegion, 1);
memory_region_init_ram(m, NULL, num_name->str,
memory->location[i].size,
&error_fatal);
...
g_string_free(name, TRUE);
>
> for (i = 0; i < memory->num; ++i) {
> MemoryRegion *m;
>
> sprintf(num_name, "%s%u", name, i);
> - m = g_malloc(sizeof(*m));
> + m = g_new(MemoryRegion, 1);
> memory_region_init_ram(m, NULL, num_name,
> memory->location[i].size,
> &error_fatal);
> @@ -55,7 +55,7 @@ static void xtensa_create_memory_regions(const XtensaMemory *memory,
> memory_region_add_subregion(get_system_memory(),
> memory->location[i].addr, m);
> }
> - free(num_name);
> + g_free(num_name);
> }
>
> static uint64_t translate_phys_addr(void *opaque, uint64_t addr)
--
Alex Bennée
next prev parent reply other threads:[~2017-05-08 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 7:35 [Qemu-devel] [PATCH] xtensa: use g_malloc/g_new/g_free Paolo Bonzini
2017-05-08 11:46 ` Philippe Mathieu-Daudé
2017-05-08 13:32 ` Alex Bennée [this message]
2017-05-08 17:05 ` Max Filippov
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=87r2zz8oep.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=jcmvbkbc@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).