From: Stefan Hajnoczi <stefanha@gmail.com>
To: mrezanin@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Prevent segmentation fault in case of relative resolve of uri
Date: Wed, 17 Sep 2014 10:26:55 +0100 [thread overview]
Message-ID: <20140917092655.GD10699@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1410248706-9769-1-git-send-email-mrezanin@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]
On Tue, Sep 09, 2014 at 09:45:06AM +0200, mrezanin@redhat.com wrote:
> From: Miroslav Rezanina <mrezanin@redhat.com>
>
> It was possible to call strcmp with NULL argument, that can cause
> segmentation fault. Properly checking parameters to prevent this
> situation.
>
> Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
> ---
> util/uri.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/util/uri.c b/util/uri.c
> index e348c17..16c01d0 100644
> --- a/util/uri.c
> +++ b/util/uri.c
> @@ -1985,7 +1985,8 @@ uri_resolve_relative (const char *uri, const char * base)
> val = g_strdup (uri);
> goto done;
> }
> - if (!strcmp(bas->path, ref->path)) {
> + if (bas->path != NULL && ref->path != NULL &&
> + !strcmp(bas->path, ref->path)) {
> val = g_strdup("");
> goto done;
> }
This patch adds more conditions, what's needed is to audit and clean up this
function. There is dead code and things could be simplified instead:
if (!strcmp(bas->path, ref->path)) {
val = g_strdup("");
goto done;
}
if (bas->path == NULL) {
val = g_strdup(ref->path);
goto done;
}
if (ref->path == NULL) {
ref->path = (char *) "/";
remove_path = 1;
}
<---- bas->path cannot be NULL because we took goto done
<---- ref->path cannot be NULL because we assigned "/"
/*
* At this point (at last!) we can compare the two paths
*
* First we take care of the special case where either of the
* two path components may be missing (bug 316224)
*/
if (bas->path == NULL) { <--- dead code!
if (ref->path != NULL) {
uptr = ref->path;
if (*uptr == '/')
uptr++;
/* exception characters from uri_to_string */
val = uri_string_escape(uptr, "/;&=+$,");
}
goto done;
}
bptr = bas->path;
if (ref->path == NULL) { <--- dead code!
Also, perhaps the strcmp() you touched should really be moved below the NULL
checks.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-17 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 7:45 [Qemu-devel] [PATCH] Prevent segmentation fault in case of relative resolve of uri mrezanin
2014-09-17 9:26 ` Stefan Hajnoczi [this message]
2014-09-18 14:54 ` Markus Armbruster
2014-09-18 14:57 ` Markus Armbruster
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=20140917092655.GD10699@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=mrezanin@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).