loc_t: add 'gfid' and 'pargfid' fields

these fields are used mainly in case of selfheal path, where
'inode->gfid'||'parent->gfid' is not yet set.

These fields in 'loc' will have lower precedence than 'inode->gfid'
in client protocol.

also contains 'Pranith <pranithk@gluster.com>'s patch to set proper
loc->gfid during afr selfheal

Signed-off-by: Amar Tumballi <amar@gluster.com>
Signed-off-by: Anand Avati <avati@gluster.com>

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

1 files changed, 11 insertions, 1 deletions

diff --git a/libglusterfs/src/xlator.h b/libglusterfs/src/xlator.h
index e587ae5784d..60fd777614a 100644
--- a/libglusterfs/src/xlator.h
+++ b/libglusterfs/src/xlator.h
@@ -78,9 +78,19 @@ typedef int32_t (*event_notify_fn_t) (xlator_t *this, int32_t event, void *data,
 struct _loc {
         const char *path;
         const char *name;
-        ino_t       ino;
         inode_t    *inode;
         inode_t    *parent;
+        /* Currently all location based operations are through 'gfid' of inode.
+         * But the 'inode->gfid' only gets set in higher most layer (as in,
+         * 'fuse', 'protocol/server', or 'nfs/server'). So if translators want
+         * to send fops on a inode before the 'inode->gfid' is set, they have to
+         * make use of below 'gfid' fields
+         */
+        uuid_t      gfid;
+        uuid_t      pargfid;
+
+        /* ideally, should not be used */
+        ino_t       ino;
 };