diff options
| author | Chris Mason <chris.mason@oracle.com> | 2011-06-24 13:13:29 -0400 |
|---|---|---|
| committer | Chris Mason <chris.mason@oracle.com> | 2011-06-24 13:13:29 -0400 |
| commit | 1973f0faeb4a5f35597793c65d3c94d8fd386e10 (patch) | |
| tree | 3e7e5c82f2cb27d679178e4787a583b05b661110 | |
| parent | e999376f094162aa425ae749aa1df95ab928d010 (diff) | |
| download | op-kernel-dev-1973f0faeb4a5f35597793c65d3c94d8fd386e10.zip op-kernel-dev-1973f0faeb4a5f35597793c65d3c94d8fd386e10.tar.gz | |
Btrfs: make sure to record the transid in new inodes
When we create a new inode, we aren't filling in the
field that records the transaction that last changed this
inode.
If we then go to fsync that inode, it will be skipped because the field
isn't filled in.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
| -rw-r--r-- | fs/btrfs/inode.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 5813dec..87f1e0c 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -4520,6 +4520,7 @@ static struct inode *btrfs_new_inode(struct btrfs_trans_handle *trans, inode_tree_add(inode); trace_btrfs_inode_new(inode); + btrfs_set_inode_last_trans(trans, inode); return inode; fail: |
