btrfs: use own btree inode io_tree owner id
authorQu Wenruo <wqu@suse.com>
Tue, 15 Sep 2020 05:35:27 +0000 (13:35 +0800)
committerDavid Sterba <dsterba@suse.com>
Wed, 7 Oct 2020 10:13:22 +0000 (12:13 +0200)
commit2c53a14dd30124de9468316933715deaf7443096
treee644a946cccd091692f9ca47715f6db2aea5b448
parent6b613cc97f0ace77f92f7bc112b8f6ad3f52baf8
btrfs: use own btree inode io_tree owner id

Btree inode is special compared to all other inode extent io_trees,
although it has a btrfs inode, it doesn't have the track_uptodate bit at
all.

This means a lot of things like extent locking doesn't even need to be
applied to btree io tree.

Since it's so special, adds a new owner value for it to make debuging a
little easier.

Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/disk-io.c
fs/btrfs/extent-io-tree.h
include/trace/events/btrfs.h