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] mkfs.gfs2: Check locktable more strictly for valid chars
Date: Mon, 15 Oct 2012 10:46:56 +0100	[thread overview]
Message-ID: <1350294416.2733.37.camel@menhir> (raw)
In-Reply-To: <1350052638-22760-1-git-send-email-anprice@redhat.com>

Hi,

Looks good. Should we also be limiting the number of : to just one I
wonder?

Steve.

On Fri, 2012-10-12 at 15:37 +0100, Andrew Price wrote:
> Previously mkfs.gfs2 allowed any printable characters to be used in the
> locktable name. This causes problems when the locktable contains special
> characters such as '/'. This patch limits the locktable to alphanumeric
> characters plus hyphens and underscores.
> 
> Ref: bz#862847
> 
> Signed-off-by: Andrew Price <anprice@redhat.com>
> ---
>  gfs2/man/mkfs.gfs2.8  | 3 ++-
>  gfs2/mkfs/main_mkfs.c | 6 ++----
>  2 files changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/gfs2/man/mkfs.gfs2.8 b/gfs2/man/mkfs.gfs2.8
> index d17e272..4613305 100644
> --- a/gfs2/man/mkfs.gfs2.8
> +++ b/gfs2/man/mkfs.gfs2.8
> @@ -73,7 +73,8 @@ Clustername must match that in cluster.conf; only members of this
>  cluster are permitted to use this file system.
>  Fsname is a unique file system name used to distinguish this GFS2 file
>  system from others created (1 to 16 characters).  Lock_nolock doesn't
> -use this field.
> +use this field. Valid \fIclustername\fRs and \fIfsname\fRs may only contain
> +alphanumeric characters, hyphens (-) and underscores (_).
>  .TP
>  \fB-V\fP
>  Print program version information, then exit.
> diff --git a/gfs2/mkfs/main_mkfs.c b/gfs2/mkfs/main_mkfs.c
> index 2d529d7..3bbb5b4 100644
> --- a/gfs2/mkfs/main_mkfs.c
> +++ b/gfs2/mkfs/main_mkfs.c
> @@ -259,10 +259,8 @@ static void test_locking(char *lockproto, char *locktable)
>  			exit(-1);
>  		}
>  		for (c = locktable; *c; c++) {
> -			if (isspace(*c))
> -				die( _("locktable error: contains space characters\n"));
> -			if (!isprint(*c))
> -				die( _("locktable error: contains unprintable characters\n"));
> +			if (!isalnum(*c) && (*c != '-') && (*c != '_') && (*c != ':'))
> +				die( _("locktable error: invalid character '%c'\n"), *c);
>  		}
>  
>  		c = strstr(locktable, ":");




  reply	other threads:[~2012-10-15  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 14:37 [Cluster-devel] [PATCH] mkfs.gfs2: Check locktable more strictly for valid chars Andrew Price
2012-10-15  9:46 ` Steven Whitehouse [this message]
2012-10-15 11:09   ` Andrew Price

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=1350294416.2733.37.camel@menhir \
    --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).