cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH gfs2-utils] don't dereference NULL for a hostdata string with no "="
Date: Thu, 02 Jul 2009 10:19:38 +0100	[thread overview]
Message-ID: <1246526378.3379.0.camel@localhost.localdomain> (raw)
In-Reply-To: <87hbxzqbd3.fsf@meyering.net>

Hi,

Looks good to me,

Steve.

On Mon, 2009-06-29 at 17:59 +0200, Jim Meyering wrote:
> I didn't try to trigger this failure, but it looks like it'd be easy to do.
> Just use a "hostdata" option, but omit the "=".
> 
> 
> >From a4d5ba668ecdabc9cbeac7a8f6ce5d227edae6b7 Mon Sep 17 00:00:00 2001
> From: Jim Meyering <meyering@redhat.com>
> Date: Mon, 29 Jun 2009 17:58:16 +0200
> Subject: [PATCH gfs2-utils] don't dereference NULL for a hostdata string with no "="
> 
> * gfs2/mount/util.c (lock_dlm_join): Instead, just ignore it.
> ---
>  gfs2/mount/util.c |    8 +++++---
>  1 files changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/gfs2/mount/util.c b/gfs2/mount/util.c
> index 57a432a..0e009bd 100644
> --- a/gfs2/mount/util.c
> +++ b/gfs2/mount/util.c
> @@ -492,9 +492,11 @@ int lock_dlm_join(struct mount_options *mo, struct gen_sb *sb)
>  	if (!mo->hostdata[0])
>  		snprintf(mo->hostdata, PATH_MAX, "%s", ma.hostdata);
>  	else {
> -		char *p = strstr(ma.hostdata, "=") + 1;
> -		strcat(mo->hostdata, ":");
> -		strcat(mo->hostdata, p);
> +		const char *p = strstr(ma.hostdata, "=");
> +		if (p) {
> +			strcat(mo->hostdata, ":");
> +			strcat(mo->hostdata, p + 1);
> +		}
>  	}
> 
>  	log_debug("lock_dlm_join: hostdata: \"%s\"", mo->hostdata);
> --
> 1.6.3.3.467.g98a79
> 



  reply	other threads:[~2009-07-02  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 15:59 [Cluster-devel] [PATCH gfs2-utils] don't dereference NULL for a hostdata string with no "=" Jim Meyering
2009-07-02  9:19 ` Steven Whitehouse [this message]
2009-07-02 11:01   ` Jim Meyering

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=1246526378.3379.0.camel@localhost.localdomain \
    --to=swhiteho@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 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).