History

btrfs: remove more obsolete v0 extent ref declarations

The extent references v0 have been superseded long time go, there are some unused declarations of access helpers. We can safely remove them now. The struct btrfs_extent_ref_v0 is not used anywhere, but struct btrfs_extent_item_v0 is still part of a backward compatibility check in relocation.c and thus not removed.

David Sterba committed 6 years ago

Commit 31344b21 parent 943aeb02 files · +0 −18Browse files

Showing the changes to include/uapi/linux (1 of 2 files). Show all

Unified · Split

include/uapi/linux/btrfs_tree.h+0−9
@@ -519,15 +519,6 @@ struct btrfs_extent_inline_ref { · 518 unmodified lines
519 __le64 offset;519 __le64 offset;
520} __attribute__ ((__packed__));520} __attribute__ ((__packed__));
521 521
522/* old style backrefs item */
523struct btrfs_extent_ref_v0 {
524 __le64 root;
525 __le64 generation;
526 __le64 objectid;
527 __le32 count;
528} __attribute__ ((__packed__));
529
530
531/* dev extents record free space on individual devices. The owner522/* dev extents record free space on individual devices. The owner
532 * field points back to the chunk allocation mapping tree that allocated523 * field points back to the chunk allocation mapping tree that allocated
533 * the extent. The chunk tree uuid field is a way to double check the owner524 * the extent. The chunk tree uuid field is a way to double check the owner

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t