From: Marcel Apfelbaum <marcel.a@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "Luiz Capitulino" <lcapitul@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 3/3] hw/machine: Free old values of string properties
Date: Mon, 02 Jun 2014 17:33:05 +0300 [thread overview]
Message-ID: <1401719585.2875.127.camel@localhost.localdomain> (raw)
In-Reply-To: <871tv7a2yj.fsf@blackfin.pond.sub.org>
On Mon, 2014-06-02 at 14:52 +0200, Markus Armbruster wrote:
> Marcel Apfelbaum <marcel.a@redhat.com> writes:
>
> > On Mon, 2014-06-02 at 13:51 +0200, Markus Armbruster wrote:
> >> Marcel Apfelbaum <marcel.a@redhat.com> writes:
> >>
> >> > On Fri, 2014-05-30 at 17:02 -0300, Eduardo Habkost wrote:
> >> >> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> >> >> ---
> >> >> Cc: Marcel Apfelbaum <marcel.a@redhat.com>
> >> >> Cc: Andreas Färber <afaerber@suse.de>
> >> >> ---
> >> >> hw/core/machine.c | 8 ++++++++
> >> >> 1 file changed, 8 insertions(+)
> >> >>
> >> >> diff --git a/hw/core/machine.c b/hw/core/machine.c
> >> >> index cbba679..df612bb 100644
> >> >> --- a/hw/core/machine.c
> >> >> +++ b/hw/core/machine.c
> >> >> @@ -24,6 +24,7 @@ static void machine_set_accel(Object *obj, const char *value, Error **errp)
> >> >> {
> >> >> MachineState *ms = MACHINE(obj);
> >> >>
> >> >> + g_free(ms->accel);
> >> > I am not sure if in QMP is not caller's responsibility to free the
> >> > input string.
> >> > If I think about it, I ask an object to set "my" string and it
> >> > deletes it :(...
> >> > Same for the others.
> >> >
> >> > Added Markus and Luiz, maybe they have an opinion on that.
> >> >
> >> >> ms->accel = g_strdup(value);
> >> >> }
> >> >>
> >>
> >> Misunderstanding? Eduardo's patch frees the old value before it
> >> overwrites it. It doesn't free "the input string", assuming by "the
> >> input string" you mean argument value.
> >
> > You are right! My bad, for some reason I saw g_free(value), but it
> > was me not reading it right :(.
>
> Happens :)
>
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
Yes indeed.
Reviewed-by: Marcel Apfelbaum <marcel.a@redhat.com>
next prev parent reply other threads:[~2014-06-02 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1401480140-18653-1-git-send-email-ehabkost@redhat.com>
[not found] ` <1401480140-18653-4-git-send-email-ehabkost@redhat.com>
2014-06-01 8:25 ` [Qemu-devel] [PATCH 3/3] hw/machine: Free old values of string properties Marcel Apfelbaum
2014-06-02 11:51 ` Markus Armbruster
2014-06-02 12:13 ` Marcel Apfelbaum
2014-06-02 12:52 ` Markus Armbruster
2014-06-02 14:33 ` Marcel Apfelbaum [this message]
[not found] ` <1401480140-18653-2-git-send-email-ehabkost@redhat.com>
2014-06-02 11:38 ` [Qemu-devel] [PATCH 1/3] rng-random: NULL check not needed before g_free() Markus Armbruster
2014-08-07 2:19 ` Amos Kong
2014-06-09 20:04 ` Luiz Capitulino
2014-06-21 15:06 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
[not found] ` <1401480140-18653-3-git-send-email-ehabkost@redhat.com>
2014-06-02 12:58 ` [Qemu-devel] [PATCH 2/3] rng-egd: Free old chr_name value before setting new one Markus Armbruster
2014-06-02 14:50 ` Eduardo Habkost
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=1401719585.2875.127.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lcapitul@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).