From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, davidagilbert@uk.ibm.com
Subject: Re: [Qemu-devel] [PATCH] block: replace unchecked strdup/malloc/calloc with glib
Date: Mon, 16 Jan 2012 12:13:43 +0100 [thread overview]
Message-ID: <4F140667.2010400@redhat.com> (raw)
In-Reply-To: <1326706086-4316-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 16.01.2012 10:28, schrieb Stefan Hajnoczi:
> Most of the codebase as been converted to use glib memory allocation
> functions. There are still a few instances of malloc/calloc in the
> block layer and qemu-io. Replace them, especially since they do not
> check the strdup/malloc/calloc return value.
>
> Reported-by: Dr David Alan Gilbert <davidagilbert@uk.ibm.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2012-01-16 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 9:28 [Qemu-devel] [PATCH] block: replace unchecked strdup/malloc/calloc with glib Stefan Hajnoczi
2012-01-16 11:13 ` Kevin Wolf [this message]
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=4F140667.2010400@redhat.com \
--to=kwolf@redhat.com \
--cc=davidagilbert@uk.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).