summaryrefslogtreecommitdiffstats
path: root/fs/Kconfig
diff options
context:
space:
mode:
authorChris Mason <chris.mason@oracle.com>2009-01-09 13:14:17 -0500
committerChris Mason <chris.mason@oracle.com>2009-01-09 13:14:17 -0500
commite293e97e363e419d8a3628a927321e3f75206a0b (patch)
tree067fb82bb4cabba35429b28c9e43f9614aea6274 /fs/Kconfig
parent755efdc3c4d3b42d5ffcef0f4d6e5b37ecd3bf21 (diff)
downloadop-kernel-dev-e293e97e363e419d8a3628a927321e3f75206a0b.zip
op-kernel-dev-e293e97e363e419d8a3628a927321e3f75206a0b.tar.gz
Btrfs: explicitly mark the tree log root for writeback
Each subvolume has an extent_state_tree used to mark metadata that needs to be sent to disk while syncing the tree. This is used in addition to the dirty bits on the pages themselves so that a single subvolume can be sent to disk efficiently in disk order. Normally this marking happens in btrfs_alloc_free_block, which also does special recording of dirty tree blocks for the tree log roots. Yan Zheng noticed that when the root of the log tree is allocated, it is added to the wrong writeback list. The fix used here is to explicitly set it dirty as part of tree log creation. Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud