diff options
| author | Shaohua Li | 2010-02-11 08:43:00 +0100 |
|---|---|---|
| committer | Chris Mason | 2010-02-12 22:47:19 +0100 |
| commit | 3f6fae9559225741c91f1320090b285da1413290 (patch) | |
| tree | 94c1a90aaed740d80cfa701b8c4abad5bbb699df /fs/btrfs/ordered-data.h | |
| parent | Btrfs: apply updated fallocate i_size fix (diff) | |
| download | kernel-qcow2-linux-3f6fae9559225741c91f1320090b285da1413290.tar.gz kernel-qcow2-linux-3f6fae9559225741c91f1320090b285da1413290.tar.xz kernel-qcow2-linux-3f6fae9559225741c91f1320090b285da1413290.zip | |
Btrfs: btrfs_mark_extent_written uses the wrong slot
My test do: fallocate a big file and do write. The file is 512M, but
after file write is done btrfs-debug-tree shows:
item 6 key (257 EXTENT_DATA 0) itemoff 3516 itemsize 53
extent data disk byte 1103101952 nr 536870912
extent data offset 0 nr 399634432 ram 536870912
extent compression 0
Looks like a regression introducted by
6c7d54ac87f338c479d9729e8392eca3f76e11e1, where we set wrong slot.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
Acked-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/ordered-data.h')
0 files changed, 0 insertions, 0 deletions