diff options
author | Raghavendra Talur <rtalur@redhat.com> | 2016-05-09 21:06:07 +0530 |
---|---|---|
committer | Pranith Kumar Karampuri <pkarampu@redhat.com> | 2016-05-10 23:03:27 -0700 |
commit | b2f09e531029f573772a09572cee0f8e1855481b (patch) | |
tree | 2d4bb90acb49334d472d689f10aedd57a0b8da0f | |
parent | 3887804d5c477de889b9f1c478be3294d9e852fd (diff) |
gfapi: clear loc.gfid when retrying after ESTALE
If an ESTALE is returned as result of a revalidate lookup, it means the
previous gfid and inode are to be discarded and lookup has to be tried
as a fresh one. A fresh lookup should not have loc.gfid set. We were
creating a new inode and passing it down but not clearing loc.gfid.
This patch fixes that.
Change-Id: Ib192ada0528b5fb5e49b4e2555f2bcab62710e2d
BUG: 1334444
Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
Reviewed-on: http://review.gluster.org/14274
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
-rw-r--r-- | api/src/glfs-resolve.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/api/src/glfs-resolve.c b/api/src/glfs-resolve.c index 7a7064c3aa2..7bfd554fe8e 100644 --- a/api/src/glfs-resolve.c +++ b/api/src/glfs-resolve.c @@ -318,6 +318,7 @@ glfs_resolve_component (struct glfs *fs, xlator_t *subvol, inode_t *parent, inode_unlink(loc.inode, loc.parent, loc.name); inode_unref (loc.inode); + gf_uuid_clear (loc.gfid); loc.inode = inode_new (parent->table); if (!loc.inode) { errno = ENOMEM; |