From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: lvm-devel@redhat.com
Subject: [PATCH] libdm: Fix memory corruption if dm_asprintf fails.
Date: Fri, 18 Oct 2013 09:47:35 +0200 [thread overview]
Message-ID: <5260E797.5060709@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1310172030470.5268@file01.intranet.prod.int.rdu2.redhat.com>
Dne 18.10.2013 02:31, Mikulas Patocka napsal(a):
> I found this bug when reading through my lvm changes.
>
> We must set the variable dmt->geometry to NULL after freeing it.
>
> dm_asprintf may fail, on failure it may not set dmt->geometry, thus
> dmt->geometry would be pointing to a free string.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>
> ---
> libdm/ioctl/libdm-iface.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Index: lvm2-copy/libdm/ioctl/libdm-iface.c
> ===================================================================
> --- lvm2-copy.orig/libdm/ioctl/libdm-iface.c 2013-10-18 02:26:07.000000000 +0200
> +++ lvm2-copy/libdm/ioctl/libdm-iface.c 2013-10-18 02:26:16.000000000 +0200
> @@ -817,6 +817,7 @@ int dm_task_set_geometry(struct dm_task
> const char *sectors, const char *start)
> {
> dm_free(dmt->geometry);
> + dmt->geometry = NULL;
> if (dm_asprintf(&(dmt->geometry), "%s %s %s %s",
> cylinders, heads, sectors, start) < 0) {
Hi
dm_asprintf() -> dm_vasprintf() -> first thing it does is: *result = 0;
So it should never return failure and leave &dmt->geometry in undefined
state. On error path it should always be set to NULL - unless there is a bug
in dm_vasprintf() which would need to be fixed.
Zdenek
prev parent reply other threads:[~2013-10-18 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 0:31 [PATCH] libdm: Fix memory corruption if dm_asprintf fails Mikulas Patocka
2013-10-18 7:47 ` Zdenek Kabelac [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=5260E797.5060709@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=lvm-devel@redhat.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.