forked from Mirrors/btrfs-progs
btrfs-progs: Sync the comment for btrfs_file_extent_item
The comment about data checksum on disk_bytes is completely wrong. Sync it with fixed kernel comment to avoid confusion. Reviewed-by: Su Yue <Damenly_Su@gmx.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>master
parent
012e51ae6e
commit
dca55d6450
12
ctree.h
12
ctree.h
|
@ -916,13 +916,16 @@ struct btrfs_file_extent_item {
|
||||||
u8 type;
|
u8 type;
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* disk space consumed by the extent, checksum blocks are included
|
* Disk space consumed by the data extent
|
||||||
* in these numbers
|
* Data checksum is stored in csum tree, thus no bytenr/length takes
|
||||||
|
* csum into consideration.
|
||||||
|
*
|
||||||
|
* The inline extent data starts at this offset in the structure.
|
||||||
*/
|
*/
|
||||||
__le64 disk_bytenr;
|
__le64 disk_bytenr;
|
||||||
__le64 disk_num_bytes;
|
__le64 disk_num_bytes;
|
||||||
/*
|
/*
|
||||||
* the logical offset in file blocks (no csums)
|
* The logical offset in file blocks.
|
||||||
* this extent record is for. This allows a file extent to point
|
* this extent record is for. This allows a file extent to point
|
||||||
* into the middle of an existing extent on disk, sharing it
|
* into the middle of an existing extent on disk, sharing it
|
||||||
* between two snapshots (useful if some bytes in the middle of the
|
* between two snapshots (useful if some bytes in the middle of the
|
||||||
|
@ -930,7 +933,8 @@ struct btrfs_file_extent_item {
|
||||||
*/
|
*/
|
||||||
__le64 offset;
|
__le64 offset;
|
||||||
/*
|
/*
|
||||||
* the logical number of file blocks (no csums included)
|
* The logical number of file blocks. This always reflects the size
|
||||||
|
* uncompressed and without encoding.
|
||||||
*/
|
*/
|
||||||
__le64 num_bytes;
|
__le64 num_bytes;
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue