nfs3: Unref & unbind dir fd with inode lock on EOFv3.1.0qa26

..so that when EOF is reached on this fd, any further
requests on the same inode do not get handled through this
fd but result in a new fd being opened.

Unbinding results in the fd getting deleted from the inode's fd list.

Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

BUG: 1619 (glusterfs nfs server crashed on dht+replica(2x2))
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1619

1 files changed, 24 insertions, 0 deletions

diff --git a/libglusterfs/src/fd.c b/libglusterfs/src/fd.c
index 9e91cdb8341..5e25b59cf91 100644
--- a/libglusterfs/src/fd.c
+++ b/libglusterfs/src/fd.c
@@ -499,6 +499,30 @@ fd_bind (fd_t *fd)
         return fd;
 }
 
+
+void
+fd_unref_unbind (fd_t *fd)
+{
+        assert (fd->refcount);
+
+        LOCK (&fd->inode->lock);
+        {
+	        --fd->refcount;
+                /* Better know what you're doing with this function
+                 * because it does not do what fd_destroy does when
+                 * refcount goes to 0.
+                 * Make sure you only call this when you know there are
+                 * pending refs on the fd.
+                 */
+                assert (fd->refcount);
+		list_del_init (&fd->inode_list);
+        }
+        UNLOCK (&fd->inode->lock);
+
+        return;
+}
+
+
 fd_t *
 fd_create (inode_t *inode, pid_t pid)
 {