qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <famz@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v4 4/6] qdev: add get_pointer_and_free() for temporary strings
Date: Fri, 21 Feb 2014 15:46:56 +0100	[thread overview]
Message-ID: <1392994018-7786-5-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1392994018-7786-1-git-send-email-stefanha@redhat.com>

get_pointer() assumes the string has unspecified lifetime (at least as
long as the object is alive).  In some cases we can only produce a
temporary string that should be freed when get_pointer() is done.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 hw/core/qdev-properties-system.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/hw/core/qdev-properties-system.c b/hw/core/qdev-properties-system.c
index 5f5957e..3bffc01 100644
--- a/hw/core/qdev-properties-system.c
+++ b/hw/core/qdev-properties-system.c
@@ -31,6 +31,20 @@ static void get_pointer(Object *obj, Visitor *v, Property *prop,
     visit_type_str(v, &p, name, errp);
 }
 
+/* Same as get_pointer() but frees heap-allocated print() return value */
+static void get_pointer_and_free(Object *obj, Visitor *v, Property *prop,
+                                 char *(*print)(void *ptr),
+                                 const char *name, Error **errp)
+{
+    DeviceState *dev = DEVICE(obj);
+    void **ptr = qdev_get_prop_ptr(dev, prop);
+    char *p;
+
+    p = *ptr ? print(*ptr) : g_strdup("");
+    visit_type_str(v, &p, name, errp);
+    g_free(p);
+}
+
 static void set_pointer(Object *obj, Visitor *v, Property *prop,
                         int (*parse)(DeviceState *dev, const char *str,
                                      void **ptr),
-- 
1.8.5.3

  parent reply	other threads:[~2014-02-21 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 14:46 [Qemu-devel] [PATCH v4 0/6] dataplane: switch to N:M devices-per-thread model Stefan Hajnoczi
2014-02-21 14:46 ` [Qemu-devel] [PATCH v4 1/6] rfifolock: add recursive FIFO lock Stefan Hajnoczi
2014-02-21 14:46 ` [Qemu-devel] [PATCH v4 2/6] aio: add aio_context_acquire() and aio_context_release() Stefan Hajnoczi
2014-02-21 14:46 ` [Qemu-devel] [PATCH v4 3/6] iothread: add I/O thread object Stefan Hajnoczi
2014-02-26 10:00   ` Igor Mammedov
2014-02-28 10:39     ` Stefan Hajnoczi
2014-02-21 14:46 ` Stefan Hajnoczi [this message]
2014-02-26  9:53   ` [Qemu-devel] [PATCH v4 4/6] qdev: add get_pointer_and_free() for temporary strings Igor Mammedov
2014-02-28 10:41     ` Stefan Hajnoczi
2014-02-21 14:46 ` [Qemu-devel] [PATCH v4 5/6] iothread: add "iothread" qdev property type Stefan Hajnoczi
2014-02-21 14:46 ` [Qemu-devel] [PATCH v4 6/6] dataplane: replace internal thread with IOThread Stefan Hajnoczi

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=1392994018-7786-5-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@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).