From: Peter Xu <peterx@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] usb: fix unbound stack usage for usb_mtp_add_str
Date: Thu, 10 Mar 2016 10:25:38 +0800 [thread overview]
Message-ID: <20160310022538.GG4091@pxdev.xzpeter.org> (raw)
In-Reply-To: <20160310015441.GF23632@ad.usersys.redhat.com>
On Thu, Mar 10, 2016 at 09:54:41AM +0800, Fam Zheng wrote:
> On Wed, 03/09 14:10, Peter Xu wrote:
> > + wchar_t *wstr = g_malloc(sizeof(wchar_t) * len);
>
> I think it is better to use g_new() in this case.
Okay. Will re-send this one.
Thanks.
Peter
next prev parent reply other threads:[~2016-03-10 2:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 6:10 [Qemu-devel] [PATCH 0/2] usb: trivial fixes Peter Xu
2016-03-09 6:10 ` [Qemu-devel] [PATCH 1/2] usb: fix unbound stack usage for usb_mtp_add_str Peter Xu
2016-03-10 1:54 ` Fam Zheng
2016-03-10 2:25 ` Peter Xu [this message]
2016-03-09 6:10 ` [Qemu-devel] [PATCH 2/2] usb: trivial cleanup " Peter Xu
2016-03-10 1:56 ` Fam Zheng
2016-03-10 6:51 ` Markus Armbruster
2016-03-10 7:42 ` Gerd Hoffmann
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=20160310022538.GG4091@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=famz@redhat.com \
--cc=kraxel@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).