From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Sarah Khan <sarahjmi07@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH][Outreachy] Signed-off-by: Sarah Khan <sarahjmi07@gmail.com>
Date: Fri, 4 Mar 2016 09:35:36 -0700 [thread overview]
Message-ID: <56D9B958.4080605@redhat.com> (raw)
In-Reply-To: <CAFEAcA-aPc-e-+-9H4ERRczQ9bbvabceUMiakGunGXOi5zrmBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
On 03/04/2016 09:06 AM, Peter Maydell wrote:
>>> +++ b/thunk.c
>>> @@ -88,7 +88,7 @@ void thunk_register_struct(int id, const char *name, const argtype *types)
>>> for(i = 0;i < 2; i++) {
>>> offset = 0;
>>> max_align = 1;
>>> - se->field_offsets[i] = malloc(nb_fields * sizeof(int));
>>> + se->field_offsets[i] = g_malloc(nb_fields * sizeof(int));
>>> type_ptr = se->field_types;
>>> for(j = 0;j < nb_fields; j++) {
>>> size = thunk_type_size(type_ptr, i);
>>
>> Where is the corresponding free()? g_malloc() must be paired with
>> g_free(), so you need to convert both places at once.
>
> There is no corresponding free(). thunk_register_struct() is called
> only at startup from the linux-user code in order to populate the
> struct_entries array; this data structure then remains live for
> the entire lifetime of the program and is automatically freed when
> QEMU exits.
Fair enough. However, g_new(int, nb_fields) is probably a bit nicer
than g_malloc() (in that it would detect multiplication overflow if
nb_fields were ever oversized).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-03-04 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 14:53 [Qemu-devel] [PATCH][Outreachy] Signed-off-by: Sarah Khan <sarahjmi07@gmail.com> Sarah Khan
2016-03-04 15:44 ` Eric Blake
2016-03-04 15:49 ` Eric Blake
2016-03-04 15:53 ` Eric Blake
2016-03-04 16:06 ` Peter Maydell
2016-03-04 16:29 ` Sarah Khan
2016-03-04 16:35 ` Eric Blake [this message]
2016-03-04 16:44 ` Peter Maydell
2016-03-04 17:09 ` [Qemu-devel] [PATCH v2][Outreachy Round 12] Sarah Khan
2016-03-05 10:42 ` Markus Armbruster
2016-03-07 5:37 ` Sarah Khan
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=56D9B958.4080605@redhat.com \
--to=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sarahjmi07@gmail.com \
/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).