summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent_io.c
diff options
context:
space:
mode:
authorYang Dongsheng <yangds.fnst@cn.fujitsu.com>2015-04-09 12:08:43 +0800
committerChris Mason <clm@fb.com>2015-04-26 06:27:03 -0700
commit6e17d30bfaf43e04d991392d8484f1c556810c33 (patch)
tree6a07d82e7c3667748e4a179aa1cb184250143947 /fs/btrfs/extent_io.c
parent909e26dce3f7600f5e293ac0522c28790a0c8c9c (diff)
downloadop-kernel-dev-6e17d30bfaf43e04d991392d8484f1c556810c33.zip
op-kernel-dev-6e17d30bfaf43e04d991392d8484f1c556810c33.tar.gz
Btrfs: fill ->last_trans for delayed inode in btrfs_fill_inode.
We need to fill inode when we found a node for it in delayed_nodes_tree. But we did not fill the ->last_trans currently, it will cause the test of xfstest/generic/311 fail. Scenario of the 311 is shown as below: Problem: (1). test_fd = open(fname, O_RDWR|O_DIRECT) (2). pwrite(test_fd, buf, 4096, 0) (3). close(test_fd) (4). drop_all_caches() <-------- "echo 3 > /proc/sys/vm/drop_caches" (5). test_fd = open(fname, O_RDWR|O_DIRECT) (6). fsync(test_fd); <-------- we did not get the correct log entry for the file Reason: When we re-open this file in (5), we would find a node in delayed_nodes_tree and fill the inode we are lookup with the information. But the ->last_trans is not filled, then the fsync() will check the ->last_trans and found it's 0 then say this inode is already in our tree which is commited, not recording the extents for it. Fix: This patch fill the ->last_trans properly and set the runtime_flags if needed in this situation. Then we can get the log entries we expected after (6) and generic/311 passed. Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com> Reviewed-by: Miao Xie <miaoxie@huawei.com> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/btrfs/extent_io.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud