From: "Alex Bennée" <alex.bennee@linaro.org>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: kwolf@redhat.com, lkurusa@redhat.com, mst@redhat.com,
jan.kiszka@siemens.com, riku.voipio@iki.fi, mjt@tls.msk.ru,
qemu-devel@nongnu.org, lcapitulino@redhat.com,
stefanha@redhat.com, luonengjun@huawei.com, pbonzini@redhat.com,
peter.huangpeng@huawei.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4 05/10] util/path: check return value of malloc()
Date: Fri, 08 Aug 2014 10:36:11 +0100 [thread overview]
Message-ID: <87oavvjozf.fsf@linaro.org> (raw)
In-Reply-To: <1407489672-12212-6-git-send-email-zhang.zhanghailiang@huawei.com>
zhanghailiang writes:
> Reviewed-by: Gonglei <arei.gonglei@huawei.com>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> ---
> util/path.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/util/path.c b/util/path.c
> index 5c59d9f..df1653f 100644
> --- a/util/path.c
> +++ b/util/path.c
> @@ -46,9 +46,12 @@ static struct pathelem *new_entry(const char *root,
> const char *name)
> {
> struct pathelem *new = malloc(sizeof(*new));
> - new->name = strdup(name);
> - new->pathname = g_strdup_printf("%s/%s", root, name);
> - new->num_entries = 0;
Erm... isn't that malloc wrong as sizeof(*new) would be the size of a
pointer?
> +
> + if (new) {
> + new->name = strdup(name);
> + new->pathname = g_strdup_printf("%s/%s", root, name);
> + new->num_entries = 0;
> + }
> return new;
> }
A better approach may be to just g_malloc which would abort on failure
(which would be fine for setup).
static struct pathelem *new_entry(const char *root,
struct pathelem *parent,
const char *name)
{
struct pathelem *new = g_malloc(sizeof(pathelem));
new->name = g_strdup(name);
new->pathname = g_strdup_printf("%s/%s", root, name);
new->num_entries = 0;
return new;
}
--
Alex Bennée
next prev parent reply other threads:[~2014-08-08 9:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 9:21 [Qemu-devel] [PATCH v4 00/10] fix three bugs about use-after-free and several api abuse zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 01/10] l2cap: fix access freed memory zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 02/10] monitor: " zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 03/10] virtio-blk: fix reference a pointer which might be freed zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 04/10] ivshmem: check the value returned by fstat() zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 05/10] util/path: check return value of malloc() zhanghailiang
2014-08-08 9:36 ` Alex Bennée [this message]
2014-08-08 10:35 ` zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 06/10] slirp/misc: " zhanghailiang
2014-08-08 9:43 ` Alex Bennée
2014-08-08 10:44 ` zhanghailiang
2014-08-08 13:24 ` Alex Bennée
2014-08-11 7:18 ` zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 07/10] linux-user: " zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 08/10] tests/bios-tables-test: check the value returned by fopen() zhanghailiang
2014-08-08 9:51 ` Alex Bennée
2014-08-08 10:46 ` zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 09/10] tcg: check return value of fopen() zhanghailiang
2014-08-08 9:21 ` [Qemu-devel] [PATCH v4 10/10] block/vvfat: fix setbuf stream parameter may be NULL zhanghailiang
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=87oavvjozf.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=jan.kiszka@siemens.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lkurusa@redhat.com \
--cc=luonengjun@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--cc=zhang.zhanghailiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.