From ac5e34ec840889bc3eaf07d2f7091432ff698fe2 Mon Sep 17 00:00:00 2001 From: Shehjar Tikoo Date: Thu, 25 Nov 2010 00:17:07 +0000 Subject: nfs: Undo selective changes in inode revalidation Those changes were brought in by commit 161850285ff06e90f2c990989bab9513dd4a4289: "nfs: re-implement logic to perform fresh lookups when lookup revalidates fail" Signed-off-by: Shehjar Tikoo Signed-off-by: Anand V. Avati BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756 --- xlators/nfs/server/src/nfs-fops.h | 6 ------ 1 file changed, 6 deletions(-) (limited to 'xlators/nfs/server/src/nfs-fops.h') diff --git a/xlators/nfs/server/src/nfs-fops.h b/xlators/nfs/server/src/nfs-fops.h index 4feb916e2..d010db282 100644 --- a/xlators/nfs/server/src/nfs-fops.h +++ b/xlators/nfs/server/src/nfs-fops.h @@ -100,12 +100,6 @@ struct nfs_fop_local { char newpath[NFS_NAME_MAX]; xlator_t *nfsx; dict_t *dictgfid; - - /* Determine whether the call was a lookup revalidate in cases where - * lookup fails. Mangle the copied loc_t to perform a fresh lookup - */ - int is_revalidate; - loc_t revalidate_loc; }; extern struct nfs_fop_local * -- cgit