Btrfs: use i_version instead of our own sequence
authorJosef Bacik <josef@redhat.com>
Thu, 5 Apr 2012 19:03:02 +0000 (15:03 -0400)
committerJosef Bacik <josef@redhat.com>
Wed, 30 May 2012 14:23:27 +0000 (10:23 -0400)
commit0c4d2d95d06e920e0c61707e62c7fffc9c57f63a
tree5d6fa736c7fea0a0afd60eda8e6e0586df6fb606
parenta25c75d5ad04df0a7abd09585231b4021a91a358
Btrfs: use i_version instead of our own sequence

We've been keeping around the inode sequence number in hopes that somebody
would use it, but nobody uses it and people actually use i_version which
serves the same purpose, so use i_version where we used the incore inode's
sequence number and that way the sequence is updated properly across the
board, and not just in file write.  Thanks,

Signed-off-by: Josef Bacik <josef@redhat.com>
fs/btrfs/btrfs_inode.h
fs/btrfs/delayed-inode.c
fs/btrfs/file.c
fs/btrfs/inode.c
fs/btrfs/ioctl.c
fs/btrfs/super.c
fs/btrfs/xattr.c