Skip to contentSkip to conversation

mkfs.gfs2: Check locktable more strictly for valid chars

PATCH New Andrew Price 2 participants 3 messages Oct 12, 2012 – Oct 15, 2012

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 mkfs.gfs2: Check locktable more strictly for valid chars

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

---
 gfs2/man/mkfs.gfs2.8  | 3 ++-
 gfs2/mkfs/main_mkfs.c | 6 ++----
 2 files changed, 4 insertions(+), 5 deletions(-)
gfs2/man/mkfs.gfs2.8 +2 -1
index d17e272..4613305 100644
@@ -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.
gfs2/mkfs/main_mkfs.c +2 -4
index 2d529d7..3bbb5b4 100644
@@ -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, ":");
Signature · 1 line
1.7.11.4
#1 lore raw

PATCH 1/1 mkfs.gfs2: Check locktable more strictly for valid chars

Hi,

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

Steve.

Quoted 44 lines · Andrew Price

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

---
 gfs2/man/mkfs.gfs2.8  | 3 ++-
 gfs2/mkfs/main_mkfs.c | 6 ++----
 2 files changed, 4 insertions(+), 5 deletions(-)
gfs2/man/mkfs.gfs2.8 +2 -1
index d17e272..4613305 100644
@@ -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.
gfs2/mkfs/main_mkfs.c +2 -4
index 2d529d7..3bbb5b4 100644
@@ -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, ":");
#2 lore raw

PATCH 1/1 mkfs.gfs2: Check locktable more strictly for valid chars

Quoted 4 lines · Steven Whitehouse

Hi,

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

That's already taken care of with a check a bit further down in that function:

         if (strstr(c, ":"))
                 die( _("locktable error: more than one colon present\n"));

Andy

Quoted 50 lines

Steve.

Quoted 44 lines · Andrew Price

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

---
  gfs2/man/mkfs.gfs2.8  | 3 ++-
  gfs2/mkfs/main_mkfs.c | 6 ++----
  2 files changed, 4 insertions(+), 5 deletions(-)
gfs2/man/mkfs.gfs2.8 +2 -1
index d17e272..4613305 100644
@@ -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.
gfs2/mkfs/main_mkfs.c +2 -4
index 2d529d7..3bbb5b4 100644
@@ -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, ":");