summaryrefslogtreecommitdiffstats
path: root/libglusterfsclient
diff options
context:
space:
mode:
authorShehjar Tikoo <shehjart@gluster.com>2009-08-28 00:17:01 +0000
committerAnand V. Avati <avati@dev.gluster.com>2009-09-02 10:30:11 -0700
commitaddf1c713a017a7b1b4a871243f599267255e815 (patch)
tree38b8b810a3c8935dbe59ffa3d4ef576dfbe80f8f /libglusterfsclient
parent22e0167d054c6880a66d51a7d86695fe2dd97f44 (diff)
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 <avati@dev.gluster.com> BUG: 209 (VMP parsing through fstab has issues) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=209
Diffstat (limited to 'libglusterfsclient')
-rwxr-xr-xlibglusterfsclient/src/libglusterfsclient.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/libglusterfsclient/src/libglusterfsclient.c b/libglusterfsclient/src/libglusterfsclient.c
index 699cd38..69be415 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;
}