diff options
| author |   Jaegeuk Kim <jaegeuk@kernel.org> | 2015-06-16 15:17:01 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2015-08-04 14:09:54 -0700 |
| commit | cbe91923a97c96d6a931f4b5b7e32083218a0251 (patch) | |
| tree | ac390209db6a60ae78d20a14fa1e932c7fe3d049 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | f2fs: fix wrong block address calculation for a split extent (diff) | |
| download | linux-dev-cbe91923a97c96d6a931f4b5b7e32083218a0251.tar.xz linux-dev-cbe91923a97c96d6a931f4b5b7e32083218a0251.zip | |
f2fs: update on-disk extents even under extent_cache
Previously, f2fs_update_extent_cache() updates in-memory extent_cache all the
time, and then finally preserves its up-to-date extent into on-disk one during
f2fs_evict_inode.
But, in the following scenario:
1. mount
2. open & write an extent X
3. f2fs_evict_inode; on-disk extent is X
4. open & update the extent X with Y
5. sync; trigger checkpoint
6. power-cut
after power-on, f2fs should serve extent Y, but we have an on-disk extent X.
This causes a failure on xfstests/311.
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions