From 95ce0a87f5fbb139f7002360d63a005bfb9c097d Mon Sep 17 00:00:00 2001 From: Shehjar Tikoo Date: Mon, 11 May 2009 18:24:34 +0530 Subject: 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 --- libglusterfsclient/src/libglusterfsclient-dentry.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'libglusterfsclient') diff --git a/libglusterfsclient/src/libglusterfsclient-dentry.c b/libglusterfsclient/src/libglusterfsclient-dentry.c index e16e304b..089a2c38 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); -- cgit