qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: "'Daniel P. Berrange'" <berrange@redhat.com>
Cc: "'Paolo Bonzini'" <pbonzini@redhat.com>,
	"'QEMU Developers'" <qemu-devel@nongnu.org>,
	"'Andreas Färber'" <afaerber@suse.de>,
	"'Markus Armbruster'" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Do not use slow [*] expansion for GPIO	creation
Date: Wed, 29 Jul 2015 17:08:18 +0300	[thread overview]
Message-ID: <01b801d0ca08$05e335b0$11a9a110$@samsung.com> (raw)
In-Reply-To: <20150729133459.GE16847@redhat.com>

 Hello!

> > +    l = strlen(name);
> > +    propname = g_malloc(l + 13); /* 10 characters for UINT_MAX plus "[]" */
> > +    memcpy(propname, name, l);
> 
> Please don't do manual string length calculations in combination with
> unbounded sprintf calls. It is a recipe for future security bugs.

[skip]

> >      for (i = gpio_list->num_in; i < gpio_list->num_in + n; i++) {
> > +        g_sprintf(&propname[l], "[%u]", i);
> 
> Replace this with
> 
>     gchar *propname = g_strdup_printf("%s[%u]", name, i)
> 
> >          object_property_add_child(OBJECT(dev), propname,
> >                                    OBJECT(gpio_list->in[i]), &error_abort);
> 
>     g_free(propname);

 IMHO it's not really good because of repeating allocation-free. This is not VERY slow, but still slower than it could be (imagine that this repeats ~1000 times).
 I have a better idea instead. What if instead:

propname = g_malloc(l + 13); /* 10 characters for UINT_MAX plus "[]" */

 i do:

propname = g_strdup_printf("%s[%u]", name, -1)

 ? This will automatically give me a buffer to fit in the largest possible integer.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia

  reply	other threads:[~2015-07-29 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 12:55 [Qemu-devel] [PATCH] Do not use slow [*] expansion for GPIO creation Pavel Fedin
2015-07-29 13:34 ` Daniel P. Berrange
2015-07-29 14:08   ` Pavel Fedin [this message]
2015-07-29 14:13     ` Daniel P. Berrange

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='01b801d0ca08$05e335b0$11a9a110$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.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).