summaryrefslogtreecommitdiff
path: root/fs/btrfs/btrfs_inode.h
diff options
context:
space:
mode:
authorChris Mason <chris.mason@oracle.com>2008-08-05 11:18:09 -0400
committerChris Mason <chris.mason@oracle.com>2008-09-25 11:04:06 -0400
commit00e4e6b33a0f78aab4b788d6d31c884fd8bf88da (patch)
tree726c1b05385f15566aa5c14ff694870f6eb6def2 /fs/btrfs/btrfs_inode.h
parent7d2b4daa67379960477568abda62b8ba9ee3a8aa (diff)
Get rid of BTRFS_I(inode)->index and use local vars instead
rename and link don't always have a lock on the source inode, and our use of a per-inode index variable was racy. This changes things to store the index in a local variable instead. Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/btrfs_inode.h')
-rw-r--r--fs/btrfs/btrfs_inode.h9
1 files changed, 0 insertions, 9 deletions
diff --git a/fs/btrfs/btrfs_inode.h b/fs/btrfs/btrfs_inode.h
index 534ac4153dd..111f90524ae 100644
--- a/fs/btrfs/btrfs_inode.h
+++ b/fs/btrfs/btrfs_inode.h
@@ -57,15 +57,6 @@ struct btrfs_inode {
* number for new files that are created
*/
u64 index_cnt;
-
- /*
- * index holds the directory index for this inode on creation, so
- * add_link can do what its supposed to. This isn't populated when the
- * inode is read because there isn't really a reason to know this unless
- * we are creating the directory index or deleting it, and deletion
- * reads the index off of the inode reference at unlink time.
- */
- u64 index;
};
static inline struct btrfs_inode *BTRFS_I(struct inode *inode)