summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorShehjar Tikoo <shehjart@zresearch.com>2009-05-11 18:24:34 +0530
committerAnand V. Avati <avati@amp.gluster.com>2009-05-18 19:13:12 +0530
commit95ce0a87f5fbb139f7002360d63a005bfb9c097d (patch)
tree69334c5009969a84539e45fc736b08b0da0ebb18
parentfe06790a3637c30dc8d5e0be7367f27ee24c36bd (diff)
libglusterfsclient: __do_path_resolve: Fix pathname resolution bug
In __do_path_resolve, we need to use the new_loc.path as the input for resolution rather than the resolved variable, simply because we're not interested in resolving the names that have been resolved, as pointed out by the variable name 'resolved'. Instead, we need to resolve new_loc, which stores the next component in the path to be looked up. Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
-rw-r--r--libglusterfsclient/src/libglusterfsclient-dentry.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/libglusterfsclient/src/libglusterfsclient-dentry.c b/libglusterfsclient/src/libglusterfsclient-dentry.c
index e16e304ba..089a2c38c 100644
--- a/libglusterfsclient/src/libglusterfsclient-dentry.c
+++ b/libglusterfsclient/src/libglusterfsclient-dentry.c
@@ -287,7 +287,7 @@ __do_path_resolve (loc_t *loc, libglusterfs_client_ctx_t *ctx,
pathname = NULL;
}
- pathname = strdup (resolved);
+ pathname = strdup (new_loc.path);
file = basename (pathname);
new_loc.inode = inode_search (ctx->itable, parent->ino, file);