From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: Max Filippov <jcmvbkbc@gmail.com>, qemu-trivial@nongnu.org
Subject: [Qemu-devel] [PATCH] xtensa: use g_malloc/g_new/g_free
Date: Mon, 8 May 2017 09:35:29 +0200 [thread overview]
Message-ID: <20170508073529.23449-1-pbonzini@redhat.com> (raw)
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);
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)
--
2.12.2
next reply other threads:[~2017-05-08 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 7:35 Paolo Bonzini [this message]
2017-05-08 11:46 ` [Qemu-devel] [PATCH] xtensa: use g_malloc/g_new/g_free Philippe Mathieu-Daudé
2017-05-08 13:32 ` Alex Bennée
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=20170508073529.23449-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jcmvbkbc@gmail.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).