From addf1c713a017a7b1b4a871243f599267255e815 Mon Sep 17 00:00:00 2001 From: Shehjar Tikoo Date: Fri, 28 Aug 2009 00:17:01 +0000 Subject: libglusterfsclient: Compare compcount with path not maxentry When searching for an exact entry we need to compare the component counts in the candidate VMP and the count in the path being searched. This is opposite to the current situation where we compare the component count in VMP and the component count in maxentry, which will always be same. Signed-off-by: Anand V. Avati BUG: 209 (VMP parsing through fstab has issues) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=209 --- libglusterfsclient/src/libglusterfsclient.c | 1 + 1 file changed, 1 insertion(+) (limited to 'libglusterfsclient') diff --git a/libglusterfsclient/src/libglusterfsclient.c b/libglusterfsclient/src/libglusterfsclient.c index 699cd38eb14..69be41516b4 100755 --- a/libglusterfsclient/src/libglusterfsclient.c +++ b/libglusterfsclient/src/libglusterfsclient.c @@ -1443,6 +1443,7 @@ _libgf_vmp_search_entry (char *path, int searchtype) vmpcompcount = 0; if ((searchtype == LIBGF_VMP_EXACT) && (maxentry)) { vmpcompcount = libgf_count_path_components (maxentry->vmp); + matchcount = libgf_count_path_components (path); if (vmpcompcount != matchcount) maxentry = NULL; } -- cgit